System and methods for tracking authorship attribution and creating music publishing agreements from metadata

ABSTRACT

Systems and methods relating to a platform for creating, monitoring, updating, and executing legal agreements for data files such as a collaborate digital media file using associated metadata. The platform enables music publishing agreements to be generated automatically by taking metadata from a DAW (digital audio workstation) that reflects the activity and contributions of each author associated with a file. Authorship metadata can be recorded on a ledger or blockchain by the platform. The platform enables calculation and disbursement of royalties to be automated by algorithmic determination of terms of an authenticated smart contract using authorship metadata for an associated media file generating the royalty. Authors may concurrently contribute from across a variety of different DAWs, local and remote, and computing resources may be distributed by the platform.

RELATED APPLICATIONS

This application is a Continuation-In-Part of U.S. application Ser. No.17/165,713 filed Feb. 2, 2021, which claims priority to U.S. ApplicationNo. 62/983,639 filed Feb. 29, 2020, which are hereby incorporated byreference herein in its entirety.

It is intended that each of the referenced applications may beapplicable to the concepts and embodiments disclosed herein, even ifsuch concepts and embodiments are disclosed in the referencedapplications with different limitations and configurations and describedusing different examples and terminology.

FIELD OF DISCLOSURE

The present disclosure generally relates to creating and filing musicpublishing agreements automatically by taking metadata from a DAW(digital audio workstation) that reflects the activity and contributionsassociated with a song.

BACKGROUND

Traditional music publishing agreements are forms that are manuallyfilled out to specify the percentage of ownerships of the song betweensongwriters. Such an agreement is filed with a music publisher and thepublisher collects the royalties on behalf of the songwriters.

Artists typically collaborate in music sessions where each musician ispresent within a studio and a session recording is made. In somesituations, artists collaborate separately where sub-groups ofmusicians, or individual musicians, record their portion(s) or track(s)at different places and at different times and then combine thoseportions and tracks to create a final work. Each artist is entitled to aroyalty based on his share of collaboration in the work. Theconventional strategy is to manually fill out forms known as publishingagreements to specify the percentage of ownerships of the song betweensongwriters. Such an agreement is filed with a music publisher and thepublisher collects royalties on behalf of the authors or copyrightholders of the work. This often causes problems because artists usuallyeither fill out the form during the period they are working on the work,or after finalizing the work. In the former case, the publishingagreement does not take into account some of the changes occurred duringthe preparation phase. In the latter case, parts of the work done bysome former artists who no longer part of the final work are missing,hence depriving them of their fair share.

BRIEF OVERVIEW

This brief overview is provided to introduce a selection of concepts ina simplified form that are further described below in the DetailedDescription. This brief overview is not intended to identify keyfeatures or essential features of the claimed subject matter. Nor isthis brief overview intended to be used to limit the claimed subjectmatter's scope.

The present disclosure can help music artist secure their publishingroyalties. As disclosed herein, copyright agreements may beautomatically generated by using contribution data for each contributingartist in associated metadata for that song to attribute authorship. Insome aspects, the song or metadata can be recorded on a ledger orblockchain. In some aspects, the present disclosure may allow forcollaboration between different users of different digital audioworkstations. In some aspects, the present disclosure may allow formechanical calculation and disbursement of royalties.

The present disclosure includes methods, systems, and computer-readablemedia for tracking authorship attribution and creating music publishingagreements from metadata. A method consistent with embodiments of thepresent disclosure begins with generating authorship metadata for a datafile. The method proceeds with receiving, from a first user, a firstcontribution to the data file. In one or more embodiments the firstcontribution includes a change in one or more data values associatedwith the data file. The method also includes evaluating the firstcontribution to produce first contribution data. The method furtherincludes recording the first contribution data in the authorshipmetadata.

The present disclosure also provides a method which begins withreceiving metadata for a data file. The method proceeds with parsing themetadata into terms. In one or more embodiments, the terms include alist of users and relative copyright ownership for each user of the listof users. Additionally, the method further proceeds with automaticallygenerating a legal document from the terms representing the relativecopyright ownership in the data file for each user of the list of users.

The present disclosure further provides a method which begins withrecording one or more changes to a data file during a digital audioworkstation session. The method proceeds with collecting user dataduring the digital audio workstation session. Additionally, the methodincludes analyzing the user data to produce analytics. In one or moreembodiments, documentation containing the analytics are generated. Themethod proceeds with storing the data file and the documentation.

The present disclosure further provides another method which begins withrunning a web browser on a computing device. The method proceeds withoperating a remote digital audio workstation using the web browser.Further, the method includes recording, in the remote digital audioworkstation, changes to a data file. The method proceeds with recording,in the remote digital audio workstation, metadata associated with thedata file.

The present disclosure further provides yet another method which beginswith determining that a rendered media file, having a plurality ofauthors, has generated a royalty. In one or more embodiments, therendered media file has associated therewith metadata containing one ormore relative authorship values for the plurality of authors. For eachauthor of the plurality of authors, a relative authorship value may beidentified from the metadata. The method proceeds with determining adisbursement amount according to the relative authorship value and theroyalty and then facilitating a payment of the disbursement amount tothe author.

Both the foregoing brief overview and the following detailed descriptionprovide examples and are explanatory only. Accordingly, the foregoingbrief overview and the following detailed description should not beconsidered to be restrictive. Further, features or variations may beprovided in addition to those set forth herein. For example, embodimentsmay be directed to various feature combinations and sub-combinationsdescribed in the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various embodiments of the presentdisclosure. The drawings contain representations of various trademarksand copyrights owned by the Applicant. In addition, the drawings maycontain other marks owned by third parties and are being used forillustrative purposes only. All rights to various trademarks andcopyrights represented herein, except those belonging to theirrespective owners, are vested in and the property of the Applicant. TheApplicant retains and reserves all rights in its trademarks andcopyrights included herein, and grants permission to reproduce thematerial only in connection with reproduction of the granted patent andfor no other purpose.

Furthermore, the drawings may contain text or captions that may explaincertain embodiments of the present disclosure. This text is included forillustrative, non-limiting, explanatory purposes of certain embodimentsdetailed in the present disclosure. In the drawings:

FIG. 1 illustrates a block diagram of an operating environmentconsistent with the present disclosure;

FIG. 2 is a flow chart of a method for providing attribution ofauthorship;

FIG. 3 is a flow chart of a method for providing generation of a legaldocument;

FIG. 4 is a flow chart of a method for providing blockchain tracking;

FIG. 5 is a flow chart of a method for providing digital audioworkstation collaboration;

FIG. 6 is a flow chart of a method for providing a mechanical royaltycalculation and disbursement;

FIG. 7 is a flow chart depicting stages for generation and execution ofa smart contract according to some embodiments;

FIG. 8 is a flow chart of a method for providing a synchronized digitalaudio workstation;

FIG. 9 is a block diagram of a system including a computing device forperforming the methods of FIGS. 2-8; and

FIGS. 10A-10K are flow charts of methods for providing synchronizeddigital audio workstation.

DETAILED DESCRIPTION

As a preliminary matter, it will readily be understood by one havingordinary skill in the relevant art that the present disclosure has broadutility and application. As should be understood, any embodiment mayincorporate only one or a plurality of the above-disclosed aspects ofthe disclosure and may further incorporate only one or a plurality ofthe above-disclosed features. Furthermore, any embodiment discussed andidentified as being “preferred” is considered to be part of a best modecontemplated for carrying out the embodiments of the present disclosure.Other embodiments also may be discussed for additional illustrativepurposes in providing a full and enabling disclosure. Moreover, manyembodiments, such as adaptations, variations, modifications, andequivalent arrangements, will be implicitly disclosed by the embodimentsdescribed herein and fall within the scope of the present disclosure.

Accordingly, while examples are described herein in detail in relationto one or more embodiments, it is to be understood that this disclosureis illustrative and exemplary of the present disclosure and are mademerely for the purposes of providing a full and enabling disclosure. Thedetailed disclosure herein of one or more embodiments is not intended,nor is to be construed, to limit the scope of patent protection affordedin any claim of a patent issuing here from, which scope is to be definedby the claims and the equivalents thereof. It is not intended that thescope of patent protection be defined by reading into any claim alimitation found herein that does not explicitly appear in the claimitself.

Thus, for example, any sequence(s) and/or temporal order of steps ofvarious processes or methods that are described herein are illustrativeand not restrictive. Accordingly, it should be understood that, althoughsteps of various processes or methods may be shown and described asbeing in a sequence or temporal order, the steps of any such processesor methods are not limited to being carried out in any particularsequence or order, absent an indication otherwise. Indeed, the steps insuch processes or methods generally may be carried out in variousdifferent sequences and orders while still falling within the scope ofthe present disclosure. Accordingly, it is intended that the scope ofpatent protection is to be defined by the issued claim(s) rather thanthe description set forth herein.

Additionally, it is important to note that each term used herein refersto that which an ordinary artisan would understand such term to meanbased on the contextual use of such term herein. To the extent that themeaning of a term used herein—as understood by the ordinary artisanbased on the contextual use of such term—differs in any way from anyparticular dictionary definition of such term, it is intended that themeaning of the term as understood by the ordinary artisan shouldprevail.

Regarding applicability of 35 U.S.C. § 112, ¶6, no claim element isintended to be read in accordance with this statutory provision unlessthe explicit phrase “means for” or “step for” is actually used in suchclaim element, whereupon this statutory provision is intended to applyin the interpretation of such claim element.

Furthermore, it is important to note that, as used herein, “a” and “an”each generally denotes “at least one,” but does not exclude a pluralityunless the contextual use dictates otherwise. When used herein to join alist of items, “or” denotes “at least one of the items,” but does notexclude a plurality of items of the list. Finally, when used herein tojoin a list of items, “and” denotes “all of the items of the list.”

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While many embodiments of the disclosure may be described,modifications, adaptations, and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to theelements illustrated in the drawings, and the methods described hereinmay be modified by substituting, reordering, or adding stages to thedisclosed methods. Accordingly, the following detailed description doesnot limit the disclosure. Instead, the proper scope of the disclosure isdefined by the appended claims. The present disclosure contains headers.It should be understood that these headers are used as references andare not to be construed as limiting upon the subjected matter disclosedunder the header.

The present disclosure includes many aspects and features. Furthermore,while many aspects and features relate to, and are described in, thecontext of digital audio workstations and automated determination ofauthorship rights to collaborative works, embodiments of the presentdisclosure are not limited to use only in this context. For example,embodiments of the present disclosure may also apply to collaborativesoftware, video, or other media generation, etc.

I. Platform Overview

This overview is provided to introduce a selection of concepts in asimplified form that are further described below. This overview is notintended to identify key features or essential features of the claimedsubject matter. Nor is this overview intended to be used to limit theclaimed subject matter's scope.

Embodiments of the present method include an authorship or metadatacontrol platform that facilitates generation of legal documents relatingto authorship, copyright ownership, and royalty disbursement by readingand writing authorship information, or data that can be used to generateauthorship information, to metadata associated with a media file. Forexample, when a user makes changes to a media file, the changes arerecorded. The metadata may be stored in, for example, a distributedledger or other blockchain based technology, providing a verified andimmutable record. Downstream, the metadata may be used for variousapplications, such as, but not limited to, determining a percentage ofownership interest in the media file associated with the metadata.Accordingly, embodiments of the present disclosure may utilize themetadata to determine relative authorship of a work and to generate apublishing contract.

Embodiments of the present disclosure may operate in conjunction with adigital audio workstation (“DAW”) or other recording/media generationapplication that music artists use to record and create songs or othermedia. In the context of the present disclosure, such applications maybe used to collaboratively create songs and to record metadatareflecting each user's contributions to the song.

In some embodiments, data points from the DAW may be collected toautomatically generate a music publishing agreement, which may bemechanically executed. In some embodiments, the data points may bestored in a metadata file. Using data science techniques, the platformmay analyze metadata and provide accurate contribution percentages,manage contracts, review contracts, and verify data kept on a ledger orblockchain. Data may be stored in a database through one of severalprocesses. The ledger or blockchain can serve as a public database thatdetails the contributions and ownership of a work (e.g., a song) inreal-time. As such, the ledger or blockchain creates a record for everyartist contribution and ownership rights to a song. The process ofupdating a digital audio workstation and its associated metadata mayoccur in real-time. Similarly, the process of updating a digital audioworkstation and its associated metadata may occur at pre-defined timeintervals (e.g., each 10 seconds, each 1 minute, every hour, every otherday, etc.). The data may be stored in its raw form or a “promise” of thedata may be stored on a ledger and analyzed by a centralized datascience platform. The results are then stored in reference to thepromised data, fulfilling the promise. This may be done sequentially, sothe data and promise may be asynchronously stored.

The following provides on example of the various embodiments disclosedherein. Consistent with embodiments of the present disclosure, data maybe collected on the various actions performed by users while they areusing one or more DAWs or similar interface to create a project file.The DAWs may be integrated with the various functionality describedherein and/or operate in conjunction with a platform providing thevarious functionality described herein.

For instance, using one or more DAWs, recording users may recorddifferent tracks to a project, editing users may modify those tracks,producer and engineer users may alter and mix the tracks. The datacaptured from those actions may be analyzed using various dataprocessing techniques (remote or locally). From that data, variousparameters may be extracted, such as, but not limited to, user profile,action performed, duration, files recorded, files modified, trackscreated, tracks edited, and various other data associated with DAWrelated action-based functions, settings, and parameters. Theseparameters may be used, for instance, to attribute authorship to theproject.

During the course of this work, a project file or files may be saved andshared between multiple DAWs, with merging of tracks between variousfiles. When a file is loaded, the DAW may be configured to retrievemetadata associated with the project file from the stored location.Embodiments of the present disclosure may track each action performed bythe DAWs and update the metadata associated with each project file basedon the actions performed. The metadata may be updated with, for example,the parameters associated with the action. In some embodiments, wheremultiple users use the same DAW, user profile information may beobtained from the DAW, digital private keys, or manually inputted by anadministrative user, or obtained through other means. Together, metadataassociated with project may be assembled and stored.

Once a file is ready for finalization, the system may generate a smartcontract. The system can pull authorship data from metadata. In one ormore embodiments, the system can prompt users to input royalty/splitsbetween authors and other interested parties. The system may also promptusers to enter publisher/distribution rights, etc.

Furthermore, the system may be configured to retrieve digital walletdata from the authors and other interested parties. Advantageously, alegal document may be generated and transmitted for execution (e.g.,e-signature). Once the legal document is signed, a digital smartcontract may be generated and then deployed. In one or more embodiments,to play the file that contains the work, it may be required that aprivate key may be retrieved.

In one or more embodiments, to retrieve a private key, digital walletinformation may be required to pay each time the file is played. Privatekey usage may be tracked. The fees collected each time the file isplayed may be disbursed to digital wallets of interested parties.

One example use of the present disclosure is the following: While usersare using a digital audio workstation, data is collected on thesoftware. In the background this data is analyzed using severalmathematical techniques (remote or locally). Upon completion of asession, or during, documentation publishing agreements are generatedreferring to the exact analytics captured during the DAW software beingused. This data is then stored in a centralized or decentralized manner.Additionally, but optionally, this data is stored, using several storageschemes (depending on the use case), in a decentralized manner such thatparticipating users can individually verify the authenticity andintegrity of the documents created, their current state, and theirhistorical information on usage, creation, changes, users associatedwith them, royalties collected, etc. The metadata recorded on the ledgermay be monitored such that when an event occurs that triggers a royalty,the disbursement to the authors occurs mechanically.

In a first aspect, the present disclosure provides a manner of givingauthorship attribution to authors of their created works. A DAW may belicensed to a particular user. In one or more embodiments, the user isthe basis for defining authorship for any file that DAW edits. The DAWmay contain in its memory user information to ensure that the DAW islinked to the appropriate user. In one or more embodiments, the DAW canbe registered with Aurign™. Accordingly, a DAW can both generate andmaintain authorship metadata.

Multiple DAWs can be configured to read and write authorship metadatafor the same raw file. As users create and edit files, each revision orcontribution is tracked and written to the metadata. If prior authors'contributions are edited or removed by a new author, the system may beconfigured to modify the relative authorship contributions (e.g., to adefault minimum contribution level). Furthermore, a DAW can be furtherconfigured to write the authorship metadata to a rendered media filethat was based on the raw DAW file.

In a second aspect, the present disclosure provides a manner forgenerating legal documents. For example, authorship metadata can be usedto generate a legal document that pertains to the copyrights, and otherlegal rights, to the created work (e.g., a song).

In a third aspect, the present disclosure provides the tracking ofactivity within a blockchain or other distributed ledger technology(DLT). Both a data file and authorship metadata can be recorded to andretrieved from a ledger. In one or more embodiments, permissions may begoverned by a recording application. The permissions may be implementedby one or more algorithms which can update the data on a song while thesong is being recorded.

Each version of a data file may have authorship metadata linkedtherewith on a digital ledger. To link a data file to its authorshipmetadata stored on a digital ledger, a hash or link connects differentversions of a song's data to the authorship metadata on the digitalledger. In one or more embodiments, once a song or other work iscreated, a folder is created on the blockchain, and within the foldercontains a history of changes made to the song.

In a fourth aspect, the present disclosure may provide DAW integrationbetween local and online DAWs. DAW integration may be used to facilitatethe operations of two or more DAWs to increase online functionality. Inone or more embodiments, an API connects DAWs instituted on localmachines to DAW instances in the cloud that is accessed by a webbrowser. DAW integration may provide a solution to the problem thatcloud-based DAW instances often lose significant functionality.Therefore, DAW integration allows users to collaborate with other usersonline, and most notably, allows users to leverage the use of localmachines to maintain the functionality and performance needed to createa song.

As such, a DAW can be configured as an online DAW for remotecollaboration. An online or cloud-based DAW instance may record changesperformed by each party (e.g., author) and record its associatedauthorship metadata.

In a fifth aspect, the present disclosure may perform mechanical royaltycalculations and disbursements. For example, when a rendered media filethat contains a work (e.g., song), is played, streamed, or performed inany manner, authorship metadata associated therewith can be used tocalculate a royalty payment to the appropriate entity. The system maythen facilitate a mechanical royalty payout. A smart contract can alsobe used to collect and distribute royalties as a trust-less custodian.

Embodiments of the present disclosure may comprise methods, systems, anda computer readable medium comprising, but not limited to, at least oneof the following:

A. A Network Layer;

B. An Authorship/Collaboration Platform Layer;

C. A DAW/Media Layer;

D. A Datastore Layer;

E. An External Device Layer;

In some embodiments, the present disclosure may provide an additionalset of layers or modules for further facilitating the software andhardware platform. The additional set of layers/modules may comprise,but not be limited to:

F. An Account Layer; and

G. A Decentralized Exchange Layer.

Details with regards to each layer/module is provided below. Althoughmodules are disclosed with specific functionality, it should beunderstood that functionality may be shared between modules, with somefunctions split between modules, while other functions duplicated by themodules. Furthermore, the name of the module should not be construed aslimiting upon the functionality of the module. Moreover, each componentdisclosed within each module can be considered independently without thecontext of the other components within the same module or differentmodules. Each component may contain language defined in other portionsof this specifications. Each component disclosed for one module may bemixed with the functionality of another module. In the presentdisclosure, each component can be claimed on its own and/orinterchangeably with other components of other modules.

The present disclosure, generally, provides for the followingaspects: 1) attribution of authorship; 2) generation of legal documents;3) data and rights tracking using distributed ledger technology; 4)collaborative environments for authorship; and 5) licensing fee trackingand distribution. It should be noted that, in various aspects of thepresent disclosure, DAW, and hence its associated metadata, can only beupdated by authorized users. That is, if the user fails theauthorization process, the unauthorized use is not allowed to make anychanges in the DAW.

Network Layer

A network layer according to some embodiments allows for transfer ofvariable-length network packets from a source to a destination host viaone or more networks. The network layer includes protocols that enablethe other layers to communicate and exchange data over a network.

Authorship/Metadata Control Platform Layer

A platform or platform layer according to some embodiments includes,inter alia, modules that may enable or facilitate automaticdetermination of authorship of a collaborative digital media file andmodules that may enable or facilitate reading, writing, and analyzingmetadata for a digital media file. In various embodiments, the platformmay be a cloud-based or web application, may be hosted on a localmachine, or may be integrated as a “plug-in” to a digital audioworkstation or other media generation software. Specific modules andfeatures of this layer are disclosed in greater detail below.

DAW/Media Layer

According to various embodiments, a DAW/Media software layer may be usedto manipulate or create a digital audio or other media file. Suchsoftware may be hosted on a local machine or may be a cloud-based or webapplication that connects to the network layer to communicate with theother layers. In some embodiments, DAW requires the user to inputidentifying information into the DAW.

DAW/Media Software layer can perform several tasks for music creationand recordation. For example, a DAW/Media Software layer may employ adigital audio processor to record, edit, and mix audio digitally. Thelayer can also employ a MIDI sequencer to record, edit, and mix MIDInotes. Further, the layer can also employ virtual instruments bytranslating MIDI information. Lastly, the DAW/Media Software layer cancreate music notations (e.g., by transforming MIDI notes into printablesheet music).

The DAW/Media Software layer can be licensed to a user who will beattributed authorship for any work stored in a file that the DAW edits.The user's information may be stored in the DAW. For example, the user'scontact information, label affiliation, management, legalrepresentation, etc. may be stored in a local or cloud-based DAW.

The DAW/Media Software layer may prompt the user to confirm that theyare the true author of the latest contribution when it is determinedthat the data file has been changed before the DAW updates theauthorship metadata. In various embodiments, a specific instance of aDAW can be registered with a third-party service that can perform one ormore aspects of the present disclosure.

Datastore Layer

According to various embodiments, a datastore layer may include local orremote storage of media files, a media bank, metadata, decentralizedledgers or blockchains, or other data storage. Data may be written to orread from the datastore layer via physical access or through connectionwith the network layer.

External Device Layer

According to various embodiments, one or more external devices may beincluded in an external device layer, either by being either connectedto a local machine or through the network layer, in the operatingenvironment. Such external devices may include, by way of non-limitingexample, musical instruments, cameras, midi controllers, handhelddevices, etc. In some embodiments, the external device layer may alsoinclude:

UI Layer

A UI Layer may be employed as an interface through which the user of auser device can send to and receive from data. The UI layer may be partof a personal device such as a smart phone or a personal computingdevice such as a desktop computer or a laptop.

API Layer

An API Layer may compile a user's commands into machine readable codesand vice versa. The API layer can be an application running on a webbrowser, or a stand-alone application running on user's device.

Account Layer

According to various embodiments, an account layer may comprise, forexample, one or more banking or financial systems. Royalties may bereceived from financial institution systems hosted on the Account Layerand processed by the platform through the network layer. In someembodiments, the platform calculates disbursements based on anyroyalties, and may distribute the disbursements to systems on theaccount layer. Such financial transactions may occur through the networklayer, or may be, for example, physically printed and mailed.

Decentralized Exchange Layer

In some embodiments, a decentralized exchange layer may be used tofacilitate financial transactions. For example, royalties anddisbursements may be received and sent to a decentralized exchange, suchas blockchain, ledger, cryptocurrency exchange or cryptocurrency wallethosted on the decentralized exchange layer. It should be noted that,throughout the present disclosure, cryptocurrency may be usedinterchangeably with any other form of digital asset or securitizedtoken and that a wallet may refer to any means by which the digitalassets may be attributable to an owner of the digital assets.

Platform Methods Overview

The following depicts a plurality of example methods that may beperformed by at least one of the aforementioned modules/layers, orcomponents thereof. Various hardware components may be used at thevarious stages of operations disclosed with reference to each module.For example, although methods may be described to be performed by asingle computing device, it should be understood that, in someembodiments, different operations may be performed by differentnetworked elements in operative communication with the computing device.For example, at least one computing device may be employed in theperformance of some or all of the stages disclosed with regard to themethods. Similarly, an apparatus may be employed in the performance ofsome or all of the stages of the methods. As such, the apparatus maycomprise at least those architectural components as found in computingdevice.

Furthermore, although the stages of the following example methods aredisclosed in a particular order, it should be understood that the orderis disclosed for illustrative purposes only. Stages may be combined,separated, reordered, and various intermediary stages may exist.Accordingly, it should be understood that the various stages, in variousembodiments, may be performed in arrangements that differ from the onesclaimed below. Moreover, various stages may be added or removed withoutaltering or deterring from the fundamental scope of the depicted methodsand systems disclosed herein.

Consistent with embodiments of the present disclosure, methods may beperformed by at least one of the modules disclosed herein. The methodsmay be embodied as, for example, but not limited to, computerinstructions stored in a tangible readable medium, which when executedby a machine, perform the method. The methods may comprise the followingstages:

Aspect 1

generating authorship metadata for a data file;

receiving, from a first user, a first contribution to the data file, thefirst contribution comprising a change in one or more data valuesassociated with the data file;

evaluating the first contribution to produce first contribution data;and

recording the first contribution data in the authorship metadata.

Aspect 2

receiving metadata for a data file;

parsing the metadata into terms, the terms comprising a list of usersand relative copyright ownership for each user of the list of users; and

automatically generating a legal document from the terms representingthe relative copyright ownership in the data file for each user of thelist of users.

Aspect 3

recording one or more changes to a data file during a digital audioworkstation session;

collecting user data during the digital audio workstation session;

analyzing the user data to produce analytics;

generating documentation containing the analytics; and

storing the data file and the generated documentation.

Aspect 4

running a web browser on a local computing device;

operating a remote digital audio workstation using the web browser;

recording, in the remote digital audio workstation, changes to a datafile; and

recording, in the remote digital audio workstation, metadata associatedwith the data file.

Aspect 5

determining that a plurality of authors of a work, which is stored in arendered media file, are due a royalty payment, the rendered media filehaving associated therewith metadata containing one or more relativeauthorship values for the plurality of authors; and, for each author ofthe plurality of authors;

identifying, from the metadata, a relative authorship value for theauthor;

determining a disbursement amount for a royalty payment according to therelative authorship value of the plurality of authors; and

facilitating a royalty payment of the disbursement amount to the author.

Although the aforementioned methods have been described to be performedby the platform, it should be understood that computing device may beused to perform the various stages of the method. Furthermore, in someembodiments, different operations may be performed by differentnetworked elements in operative communication with computing device. Forexample, a plurality of computing devices may be employed in theperformance of some or all of the stages in the aforementioned method.Moreover, a plurality of computing devices may be configured much like asingle computing device. Similarly, an apparatus may be employed in theperformance of some or all stages in the method. The apparatus may alsobe configured much like computing device.

According to an aspect of the present disclosure, a method forsynchronized digital audio workstation is disclosed. The methodcomprises steps of identifying, from a user device, a first digitalaudio workstation (DAW) instance, wherein the first DAW comprises atleast an identification of a user of the user device and an audio datafile; determining whether the user of the user device is an authorizeduser; and generating a first metadata based at least in part on at leastone action performed by the first DAW, wherein the first metadatacomprises a first contribution value by the user to the audio data file.

According to another aspect of the present disclosure, a method forsynchronized digital audio workstation operations is disclosed. Themethod comprises steps of obtaining, from a user device, a first digitalaudio workstation (DAW) instance, wherein the first DAW comprises atleast an identification of a user of the user device and an audio datafile; generating a first metadata based at least in part on at least oneaction performed by the first DAW, wherein the first metadata comprisesa first contribution value by the user to the audio data file;generating a first document based on the first DAW and first metadata,wherein the first document comprises information about copyrights of theaudio data file.

According to yet another aspect of the present disclosure, a method forsynchronized digital audio workstation operations is disclosed. Themethod comprises steps of identifying, from a user device, a firstdigital audio workstation (DAW) instance, wherein the first DAWcomprises at least an identification of a user of each user device andan audio data file; generating a first metadata based at least in parton at least one action performed within the first DAW, wherein the firstmetadata comprises a first contribution value by each user to the audiodata file; calculating a share for each user based on a number of timesthe audio data file is streamed or played and the first contributionvalue by the user to the audio data file; and generating a first ledgerfor the first DAW based at least in part on the calculated share and thefirst DAW.

According to still another aspect of the present disclosure, a methodfor synchronized digital audio workstation provision are disclosed. Themethod comprises steps of providing a first DAW associated with a firstuser device, wherein the first DAW comprises at least one of a firstidentification of a user of the first user device and an audio datafile; receiving a request from a second user device to access the firstDAW; upon determining that the second user device is an authorized userdevice, granting, to second user device, access to the first DAW;updating the first DAW by adding a second identification of a user ofthe second user device; and generating a first metadata based at leastin part in the first DAW, wherein the first metadata comprises a firstcontribution value by the first user to the audio data file and a secondcontribution by the second user to the audio data file. DAW integrationallows users to collaborate with other users online, and most notably,allows users to leverage the use of local machines to maintain thefunctionality and performance needed to create a song.

According to another aspect of the present disclosure, a method forsynchronized digital audio workstation provision is disclosed. Themethod comprises steps of identifying a first digital audio workstation(DAW) instance, wherein the first DAW comprises at least anidentification of a user of each user device associated with the firstDAW and an audio data file; generating a first metadata based at leastin part on the first DAW, wherein the first metadata comprises a firstcontribution value to the audio data file for the user of each userdevice; and calculating, for the user of each user device, a share basedon a number of times the audio data file is streamed or played and thefirst contribution value associated with the user.

Both the foregoing overview and the following detailed descriptionprovide examples and are explanatory only. Accordingly, the foregoingoverview and the following detailed description should not be consideredto be restrictive. Further, features or variations may be provided inaddition to those set forth herein. For example, embodiments may bedirected to various feature combinations and sub-combinations describedin the detailed description.

II. Platform Configuration

FIG. 1 illustrates one possible operating environment through which aplatform consistent with embodiments of the present disclosure may beprovided. By way of non-limiting example, an authorship/metadataanalysis platform may be hosted on, for example, a cloud computingservice. In some embodiments, the platform may be hosted on a computingdevice. A user may access platform through a software application and/orhardware device. The software application may be embodied as, forexample, but not be limited to, a website, a web application, a desktopapplication, and a mobile application compatible with the computingdevice. One possible embodiment of the software application and/orhardware device may be provided by a suite of products and servicesprovided by Aurign™.

FIG. 1 further illustrates one possible operating environment throughwhich a platform consistent with embodiments of the present disclosuremay be provided. By way of non-limiting example, a platform 100 forproviding the methods and systems for may be hosted in both a blockchainprotocol (“on-chain”) and off of a blockchain protocol (“off-chain”).One possible embodiment of the platform 100 may be provided by theEthereum protocol provided by ethereum.org. It should be understood byone having ordinary skill in the art that layers and stages performed bythe layers may be either “on-chain” or “off-chain.” The presentdisclosure anticipates embodiments with variations as to which stagesmay be performed “on-chain” or “off-chain.” It should also be understoodby one having ordinary skill in the art that “on-chain” or “off-chain”layers or stages may be implemented as protocols for doing a particular,well-defined, circumscribed function.

Accordingly, embodiments of the present disclosure provide a softwareand hardware platform, implemented within one or more networkarchitectures and protocols, comprised of a distributed set of computingelements, including, but not limited to:

A. Metadata Protocol Module

According to various embodiments, the platform 100 may include ametadata protocol module. The metadata protocol module may includesub-modules for reading metadata, writing metadata, analyzing metadata,and generating metadata. For example, the metadata protocol module maygenerate authorship metadata from a log of changes to a digital mediafile. The authorship data may then be recorded in metadata associatedwith the file. After the file has been changed multiple times bydifferent users, the metadata protocol module may read the metadata andanalyze the authorship data to determine relative authorship for eachuser who made a contribution to the file. The metadata protocol modulein some embodiments may send and receive digital media files or metadatafrom the DAW/software layer.

In the event that the contribution by an author is deleted from the datafile, the metadata protocol module may institute a sub-routine todetermine whether the author of the deleted contribution is deserving ofauthorship in the final work. For example, if it is determined that thedetected contribution led to the final work (e.g., a song) due to theevolutionary nature of the created work, the DAW, for example, mayassign an authorship value to the author for royalties (e.g., a minimumpre-determined authorship value). Advanced techniques such as machinelearning may be used to determine the relative authorship values forauthors whether their contributions were deleted from or were maintainedin the final work.

B. Blockchain Protocol Module

According to various embodiments, the platform 100 may include ablockchain protocol module. The blockchain protocol module may read andwrite metadata and authorship information to a decentralized ledger orblockchain. Additionally, the blockchain protocol module may facilitatetransfer of digital or cryptocurrency, such as by reading transactionsfrom, writing transactions to, or validating transactions on ablockchain or ledger. In some embodiments, the blockchain protocolmodule may periodically monitor one or more ledgers or blockchains forchanges in a digital media file and may automatically inform anothermodule or layer of the change, for example, when it is determined thatone or more authors of a work are due a royalty payment which may berecorded in a ledger, the blockchain protocol will detect the changeduring the next periodic monitoring and may inform the documentgeneration module or contract module in near real-time. In variousembodiments, the blockchain protocol module can facilitate the processof writing data to a sequence of blocks in a blockchain framework,particularly, an Ethereum framework. For Ethereum frameworks, blocksizes are not limited and are capable of storing authorship metadataalong with records associated with digital currency transactions. Insome embodiments, a peer-to-peer file system is implemented within anEthereum blockchain framework to facilitate file storage.

C. Network Communication Module

According to some embodiments, a network communication module may enableor facilitate connection of the platform 100 to the network layer or todevices in networked communication with the platform. The networkcommunication module may also allow the platform to monitor networkeddevices such as computing systems, cloud environments, or datastores.

D. Document Generation Module

According to some embodiments, a document generation module mayfacilitate generation or modification of documents. The documentgeneration module may receive data from or generate information fromdata received from the metadata protocol module. The document generationmodule may also receive data, such as user information, bank accountinformation, cryptowallet information, etc., from the financialtransaction module, the account layer, the decentralized exchange layer,the DAW layer etc. The document generation module may extract terms fromreceived data and create various documents in various formats such as,but not limited to, legal documents, contracts, royalty agreements,copyright agreements, copyright application forms, or other legaldocuments.

E. Contract Generation Module

According to various embodiments, a contract generation module maygenerate a contract based on terms generated from data received by thedocument generation module.

In some embodiments, the contract generation module may be a sub-moduleof the document generation module. The contract generated may be a“smart contract.” For example, a smart contract may include a set ofrules, conditions, or events that algorithmically or mechanicallydetermine when the contract is executed and under which terms. Terms ofthe smart contract may be automatically updated by periodic monitoringof data regarding, for example, authorship and royalty generation,changes in law, property assignments, or changes in contract terms. Whena royalty event is detected, a smart contract may mechanically updateterms, such as authorship percentages (e.g., relative authorshipvalues), to reflect any changes to the media file or associatedmetadata. The contract generation module may communicate with theauthentication module to determine whether a contract has been signed orotherwise authorized before being executed.

F. Authentication Module

The various implementations, the authentication module may be asub-module of the document generation module or the contract generationmodule. In some embodiments, an authentication module may generatee-signature requests or may validate or verify that a signature orauthentication has been received. Authentication may be obtained, forexample, by an e-signature service connected to the network layer,through user information received from a DAW user account, or throughanother layer or module. In some embodiments, once authentication hasbeen received for each party to a contract, the authentication modulemay automatically provide verification to the contract generation modulefor execution of a contract.

G. Financial Transaction Module

According to some embodiments, a financial transaction module may beincluded in the platform. The financial transaction module may receiveuser (author, producer, label, etc.) information, such as payment orfinancial account information or other information used to send andreceive payments. The financial transaction module may includesub-modules to facilitate the receipt and disbursement of royaltypayments to authors. For example, royalty payments may be achieved bysending, receiving or processing a physical check or electronic moneytransfer, or by reading from, writing to, or verifying a transaction ona decentralized ledger or blockchain.

H. Collaboration Module

According to some embodiments, the platform 100 may include acollaboration module. The collaboration module may include sub-modulessuch as an application programming interface to enable or facilitatecollaboration between authors of a collaborative work that is stored inaa digital media file. For example, the collaboration module may monitoror analyze simultaneous contributions by multiple artists to a digitalmedia file during a session. The artists may collaborate differentcomputing devices or network of synchronized DAWs connected via anetwork to create a work. The collaboration module may record andanalyze the respective changes to the file made by each user, andcompute authorship data reflecting the relative contributions of eachauthor during the session, which may then be provided to the metadataprotocol layer.

I. Resource Management Module

According to various embodiments, the platform 100 may be hosted on adistributed network of computing devices. The platform 100 may analyzethe resource use, such as the percentage of CPU or RAM being used, foreach machine, and may distribute tasks across the networked devices tooptimize performance. Different users may require different resourceconsumption at different times, or may have differing resourceavailability on their devices. By managing the resources used, multipleusers may “share” computing resources to improve performance.Additionally, computing devices not associated with a particular usermay be in a networked connected to the platform 100. Computing resourceson such a device may also be accessible by users of the platform 100 toimprove performance.

J. Software Integration Module

According to various embodiments, a software integration module mayinclude protocols for allowing operative networked communication withvarious software platforms, such as DAWs or other media creationsoftware. The software integration module may enable the platform 100 tobe used as a “plug-in” or otherwise incorporated into or operable withdiverse software.

III. Platform Operation

Embodiments of the present disclosure provide a hardware and softwareplatform operative by a set of methods and computer-readable mediacomprising instructions configured to operate the aforementioned modulesand computing elements in accordance with the methods. The followingdepicts a plurality of example methods that may be performed by at leastone of the aforementioned modules. Various hardware components may beused at the various stages of operations disclosed with reference toeach module.

For example, although methods may be described to be performed by asingle computing device, it should be understood that, in someembodiments, different operations may be performed by differentnetworked elements in operative communication with the computing device.For example, at least one computing device 900 may be employed in theperformance of some or all of the stages disclosed with regard to themethods. Similarly, an apparatus may be employed in the performance ofsome or all of the stages of the methods. As such, the apparatus maycomprise at least those architectural components as found in computingdevice 900.

Furthermore, although the stages of the following example methods aredisclosed in a particular order, it should be understood that each orderis disclosed for illustrative purposes only. Stages may be combined,separated, reordered, and various intermediary stages may exist.Accordingly, it should be understood that the various stages, in variousembodiments, may be performed in arrangements that differ from the onesclaimed below. Moreover, various stages may be added or removed withoutaltering or deterring from the fundamental scope of the depicted methodsand systems disclosed herein.

A. Master Methods

Consistent with embodiments of the present disclosure, the followingmethods may be performed by at least one of the aforementioned modules.The methods may be embodied as, for example, but not limited to,computer instructions, which when executed, perform the method. Themethods may respectively comprise the following stages:

Aspect 1

FIG. 2 is a flow chart setting forth the general stages involved in amethod 200 consistent with an embodiment of the disclosure for providingauthorship platform 100. Method 200 may be implemented using a computingdevice 900 or any other component associated with platform 100 asdescribed in more detail below with respect to FIG. 9. For illustrativepurposes alone, computing device 900 is described as one potential actorin the following stages.

Method 200 may begin at starting block and proceed to stage 220 wherecomputing device 900 may generate authorship metadata for a data file.

From stage 220, where computing device 900 generates authorshipmetadata, method 200 may advance to stage 230 where computing device 900may receive a first contribution to the data file from a first user. Thefirst contribution may comprise a change in one or more data valuesassociated with the data file. For example, changes to a data file mayrelate to a part of a song being recorded by a user, such as a musician(e.g., music producer) of a digital audio workstation.

Once computing device 900 receives the first contribution in stage 230,method 200 may continue to stage 240 where computing device 900 mayevaluate the first contribution to produce first contribution data. Invarious embodiments, evaluating the first contribution may includedetermining whether a change to the authorship metadata is warranted.For example, if the first contribution constitutes an insignificantchange to the work, such as a change to the filename of the data file,no change will be made to the authorship metadata. The primary objectiveof stage 230 is to ensure that authors receive proper credit andattribution for their contributions.

After computing device 900 evaluates the first contribution in stage240, method 200 may proceed to stage 250 where computing device 900 mayrecord the first contribution data in the authorship metadata. Forexample, the authorship metadata may be automatically recorded when achanged data file is saved in a digital audio workstation, such as bybeing written onto a digital media file in a digital audio workstationor other media generation software application. Further, the digitalaudio workstation may have account information related to a present userof the DAW, such as authentication information, bank accountinformation, personal information, etc.

In some embodiments, a raw media file created in a digital audioworkstation without metadata, or without authorship metadata asdisclosed herein may have authorship metadata written onto it to producea media file with associated authorship metadata.

According to various embodiments, the authorship metadata may berecorded on a ledger, blockchain, or other centralized or decentralizeddatastore.

Once computing device 900 records the first contribution data in stage250, method 200 may then end at stage.

In some embodiments, the method 200 may further comprise receiving asecond contribution to a data file from a second user. The secondcontribution may also comprise a change in one or more data valuesassociated with the data file. The second contribution may be evaluatedto produce second contribution data. The authorship metadata may bemodified based on the second contribution data, or the first and secondcontribution data. A relative authorship value may then be determinedfor the first and second user. Similarly, a plurality of users may makea plurality of contributions. The contributions may be analyzed toproduce a plurality of contribution data, and a relative authorshipvalue may be determined for each user. Further, one or more users may beusing a different digital audio workstation to make respectivecontributions to the data file. The DAWs may be hosted on local orremote computing devices or may be in the form of a cloud-based or webapplication. The different digital audio workstations may each use amodule as disclosed herein to generate, read, edit, change, monitor, orotherwise interact with authorship metadata. Additionally, theauthorship data may also be written to a ledger or blockchain, which maybe decentralized, or a remote data storage, and read or monitoredoutside of the DAW(s).

In some embodiments, one or more contributions to a data file may beevaluated in real time as the contribution is being made to producecontribution data. Further, multiple users may simultaneously makecontributions which may be together evaluated in real time. Suchevaluation may determine, algorithmically, an authorship value which maybe written into metadata for the file. Still further, machine learningmay be used to evaluate the contributions, for example, by optimizingthe algorithmic determination of attribution of authorship based on datapoints reflecting changes to a digital media file. For example, datapoints related to a song may include the effect of the change to theoverall song, the time spent by the user when making changes to thesong, etc.

Aspect 2

FIG. 3 is a flow chart setting forth the general stages involved in amethod 300 consistent with an embodiment of the disclosure for providingauthorship platform 100. Method 300 may be implemented using a computingdevice 900 or any other component associated with platform 100 asdescribed in more detail below with respect to FIG. 9. For illustrativepurposes alone, computing device 900 is described as one potential actorin the follow stages.

Method 300 may begin at starting block and proceed to stage 320 wherecomputing device 900 may receive metadata for a data file. For example,the metadata may contain authorship information for a digital media filewhich may be read by a DAW.

From stage 320, where computing device 900 receives metadata, method 300may advance to stage 330 where computing device 900 parses the metadatainto terms. The terms may comprise a list of users and relativecopyright ownership or authorship percentage for each user in the list.Other information may also be available and parsable from the metadata.

Once computing device 900 parses the metadata in stage 330, method 300may continue to stage 340 where computing device 900 automaticallygenerates a legal document from the parsed terms representing therelative copyright ownership in the work stored in the data file foreach user in the list of users. For example, the legal documents may berelated to any form used to prepare a copyright application, royaltyagreement, etc. The generated legal documents may express a transfer ofproperty rights to the created work. For example, the legal documentsmay include one or more single song agreements, exclusive song writeragreements, co-publishing agreements, administration agreements,collection agreements, sub-publishing agreements, merchandisingagreements, synchronization agreements, licensing agreements, purchasingagreements, etc.

After computing device 900 generates the legal document in stage 340,method 300 may end at stage.

In some embodiments, the method 300 may further comprise a manner tofacilitate obtaining a signature or authorization from each user of thelist of users in stage 306. The signature or authorization may berequired for completion of royalty disbursement.

The legal documents may also specify the ownership rights in derivativeworks. In various embodiments, the legal document generated may be aprinted contract or a smart contract, a royalty agreement, a copyrightregistration form or document, and may be recorded on a ledger orblockchain. A smart contract may include rules which govern whethercertain transactions occur (e.g., the generation of legal documents inresponse to changes in data files).

In some embodiments, the method 300 may further comprise detecting thata royalty payment associated with the data file has been made andautomatically disbursing the royalty payment to each contributing useraccording to the relative copyright ownership or authorship representedin the legal document. The royalty and other payments may be facilitatedby the financial transaction module.

Aspect 3

FIG. 4 is a flow chart setting forth the general stages involved in amethod 400 consistent with an embodiment of the disclosure for providingauthorship platform 100. Method 400 may be implemented using a computingdevice 900 or any other component associated with platform 100 asdescribed in more detail below with respect to FIG. 9. For illustrativepurposes alone, computing device 900 is described as one potential actorin the follow stages.

Method 400 may begin at starting block and proceed to stage 420 wherecomputing device 900 may record one or more changes to a data fileduring a digital audio workstation session.

From stage 420, where computing device 900 records one or more changes,method 400 may advance to stage 430 where computing device 900 maycollect user data during the digital audio workstation session. Forexample, the user data may comprise a log of any changes to the datafile and the method may further comprise analyzing the log to producethe authorship data. The log of changes may contain the identity of theuser which made the change to the data file, a timestamp of the change,and the change made to the work that is embodied in the data file. Invarious embodiments, the DAWs are equipped with permissions to determinewhether one or more users can effect changes to authorship metadata andrelative authorship values in response to changes to a data file. Forexample, if a new song has been completed, such as a master recording,permissions may be set such that unauthorized changes to a data file areprevented such that no changes are made to the authorship metadata andrelative authorship values.

Moreover, each version of the data file may be stored “on-chain” or“off-chain” along with the authorship metadata and relative authorshipvalues associated therewith and can be retrieved upon the execution ofsmart contracts.

Once computing device 900 collects the user data in stage 430, method400 may continue to stage 440 where computing device 900 may analyze theuser data to produce analytics. For example, a log of changes can beanalyzed to determine the time a user spent making the contributions tothe work stored in the data file, the degree of transformation to thework, etc. Furthermore, analyzing the user data may include sorting,aggregating, and summarizing the data in one or more legal agreements(e.g., publishing contract).

After computing device 900 analyzes the user data in stage 440, method400 may proceed to stage 450 where computing device 900 may generatedocumentation containing the analytics. In some embodiments, a digitalaudio workstation incorporating modules of the authorship platform 100as described herein may use one or more of the modules to generate andstore, for example, the analytics documentation, data file, and/orassociated metadata in a centralized or decentralized manner, e.g., on ablockchain.

After computing device 900 generates documentation in stage 450 ofmethod 400, method 400 may proceed to stage 460 where computing device900 stores the data file and/or the documentation. In various exampleembodiments, the analytics documentation and/or data file may be locallyor remotely stored, in or on, for example, a ledger or blockchain. Oncecomputing device 900 stores the data file and analytics documentation instage 460, method 400 may then end at stage.

According to various embodiments, the method 400 may further comprisechanging one or more portions of a data file during a plurality ofdigital audio workstation sessions to produce a plurality of sessiondata files and, for each digital audio workstation session, collectingsession user data during the digital audio workstation session;recording a session data file; analyzing the session user data toproduce session analytics; generating associated session documentationcontaining the session analytics; and storing the session data file andassociated session documentation for the digital audio workstationsession. In some embodiments, each session data file and/or associatedmetadata may be stored on a ledger or blockchain. The metadata maycontain the associated session documentation for the session data file.

In some embodiments, the method 400 may further comprise generating ahash value for the data file. In some embodiments, the hash value may berecorded in the analytics documentation. In some embodiments, a hashvalue may be generated for each DAW session of a plurality of DAWsessions. The hash values may then be recorded in the analyticsdocumentation for each associated session. This may enable faster ormore efficient processing, monitoring, version control, or validation ofdocumentation associated with a data file.

Aspect 4

FIG. 5 is a flow chart setting forth the general stages involved in amethod 500 consistent with an embodiment of the disclosure for providingauthorship platform 100. Method 500 may be implemented using a computingdevice 900 or any other component associated with platform 100 asdescribed in more detail below with respect to FIG. 9. For illustrativepurposes alone, computing device 900 is described as one potential actorin the follow stages.

Method 500 may begin at starting block and proceed to stage 520 wherecomputing device 900 may run a web browser. For example, a localcomputing device may run a web browser suitable for operating a web orcloud based digital audio workstation.

From stage 520, where computing device 900 runs the web browser, method500 may advance to stage 530 where computing device 900 may operate aremote digital audio workstation using the web browser.

Once computing device 900 operates the digital audio workstation instage 530, method 500 may continue to stage 540 where computing device900 may record, in the remote digital audio workstation, changes to adata file.

After computing device 900 records changes to the data file in stage540, method 400 may proceed to stage 550 where computing device 900 mayrecord, in the remote digital audio workstation, metadata associatedwith the data file. For example, the authorship metadata associated withthe user of the remote digital audio workstation may be stored in thecloud or in any storage associated with the remote digital audioworkstation. In various embodiments, the metadata may be stored in anassigned local DAW (e.g., a network of shared DAWs). For example, oncecomputing device 900 records the metadata in stage 550, method 500 maythen end at stage.

According to various embodiments, the method 500 may further compriserunning a plurality of web browsers on a plurality of computing devices.The plurality of web browsers may be used to operate one or more remotedigital audio workstations during one or more DAW sessions. In variousembodiments, one or more DAWs may facilitate the use by a plurality ofusers so long as they are authorized to operate the hardware and/orsoftware to create or edit a work. The digital audio workstations may beused to make changes to a data file, such as recording parts of a song.Each change may be recorded in the associated digital audio workstation.The DAWs may have incorporated therein modules of the platform asdisclosed herein. Accordingly, metadata associated with each session maybe recorded in the respective DAW used to make changes to the data file.As previously described, when a plurality of DAWs are used concurrentlyto make changes to a data file, the collaborative module may be employedto prevent multiple change requests to the same segment(s) concurrently.

In some embodiments, one or more of the remote digital audioworkstations may use resources of the computing device. For example, aweb browser on a local computing device may access a DAW, and the DAWmay access resources on the local computing device. Similarly, aplurality of devices may each be used to access DAWs, and the resourcesavailable on each device may be distributed among the devices. Further,decentralized or cloud-based computing devices, which may not belong toa specific user, may have resources partitioned therefrom by users ofthe platform 100. As such, computation offloading may be implemented totransfer resource-intensive computation tasks to a separate processor(e.g., hardware accelerator, or an external platform. Offloadingcomputing to an external platform (e.g., cluster, grid, or cloud) over anetwork can provide computing power and overcome hardware limitations ofa device, particularly, limited computational power, storage, andenergy. In various embodiments, less resource-intensive tasks (e.g.,storing authorship metadata) may be offloaded to a remote digital audioworkstation. Resource-intensive tasks may be assigned to one or morelocal digital audio workstations.

Aspect 5

FIG. 6 is a flow chart setting forth the general stages involved in amethod 600 consistent with an embodiment of the disclosure for providingauthorship platform 100. Method 600 may be implemented using a computingdevice 900 or any other component associated with platform 100 asdescribed in more detail below with respect to FIG. 9. For illustrativepurposes alone, computing device 900 is described as one potential actorin the follow stages.

Method 600 may begin at starting block and proceed to stage 620 wherecomputing device 900 may determine that a plurality of authors of a workstored in a rendered media file are due a royalty payment. The renderedmedia file may have associated therewith metadata containing one or morerelative authorship values for the plurality of authors.

From stage 620, where computing device 900 determines that a pluralityof authors of a work stored in a rendered media file are due royaltypayments, method 600 may advance to stage 630 where computing device 900may, for each author of the plurality of authors, identify, from themetadata, a relative authorship value for the author.

Once computing device 900 determines the relative authorship value foreach author in stage 630, method 600 may continue to stage 640 wherecomputing device 900 may, for each author of the plurality of authors,determine a disbursement amount for the royalty payment according to therelative authorship value for each author. In some embodiments, one ormore of the authors may use a digital audio workstation to makecontributions to the data file. The digital audio workstations maycontain user information related to authors. This user information maybe used to facilitate disbursements for the authors. For example, userinformation in the DAW may include, inter alia, contact information,such as a name, phone number, email address, or physical address, bankaccount information, cryptowallet information, and other accountinformation.

After computing device 900 determines a disbursement amount for eachauthor in stage 640, method 600 may proceed to stage 650 where computingdevice 900 may, for each author of the plurality of authors, facilitatea payment of the disbursement amount for that author to the author. Oncecomputing device 900 facilitates payment of the royalty in stage 650,method 600 may then end at stage.

According to some embodiments, the method 600 may further compriseparsing, from the metadata, the authorship values and automaticallygenerating an enforceable legal document apportioning copyrightownership, authorship, or royalty rights in the work stored in the mediafile based on the parsed authorship values.

According to some embodiments, the method 600 may further comprisereceiving an agreement to or authorization for, such as a signature, asmart contract, from each author. The agreement to the smart contractmay comprise an agreement to an apportionment of copyright ownership,authorship, or royalty rights in a work stored in the media file. Therights or attribution of authorship may be based on the parsedauthorship values. In various embodiments, an executed agreement byinterested parties to a work stored in the media file may be stored asdata within a smart contract. A change to the smart contract (e.g., achange in the relative authorship values) can change the state of thesmart contract within an Ethereum framework.

In some embodiments, the method 600 may further comprise recording achange to the rendered media file made by a first user in a firstdigital audio workstation that results in a changed rendered media file.The change to the media file may then be evaluated to produce authorshipdata for the first user. The authorship data may then be recorded in theauthorship metadata for the changed rendered media file. The method 600may further comprise identifying a first relative authorship value forthe first user from the metadata. A first disbursement amount may becalculated according to the first relative authorship value. The method600 may also comprise facilitating a royalty payment of the firstdisbursement amount to the first user as described in more detail below.

Similarly, the method 600 may comprise recording a change to therendered media file made by a plurality of users in one or more digitalaudio workstations that results in changed rendered media files. Thechanges to the media file may then be evaluated to produce authorshipdata for each user of the plurality of users. The authorship data maythen be recorded in the metadata for the each changed rendered mediafile. The method 600 may further comprise identifying a plurality ofrelative authorships value for each user from the metadata. A pluralityof disbursement amounts may be calculated according to the relativeauthorship values. The method 600 may also comprise facilitatingpayments of the plurality of royalty payments to one or more authors.

According to some embodiments, payments to a user or plurality of usersof one or more DAWs may be automated using account information for auser account or plurality of user accounts belonging to the user orplurality of users of the one or more DAWs.

In yet other embodiments, the method 600 facilitates the payment ofroyalties within an Ethereum-blockchain framework. An Ethereum frameworkcan facilitate decentralized transactions in a Turing-complete executionenvironment and therefore can perform any computation such as analgorithm. Smart contracts can be executed these computations, and foreach transaction, a computation is executed within Ethereum.

In various embodiments, smart contracts can hold any arbitrary state andcan perform any arbitrary computation. Advantageously, smart contractscan call other small contracts and can hold data.

For example, authorship metadata and the relative authorship values maybe stored as data. For instance, during a DAW session, when theauthorship metadata is updated due to changes to a data file, the stateof one or more smart contract changes.

In various embodiments, the change in state of a first smart contract,which stores the authorship metadata, triggers a second smart contractwhich stores the data associated with the relative authorship values ofeach author listed in the authorship metadata.

A third smart contract can store data associated with an account used tomake royalty payments. In various embodiments, the third smart contractinitiates royalty payments in the form of an ether (or other suitablecryptocurrency) to an account owned by the authors (copyright holders,etc.), subject to a set of rules, conditions, or events thatalgorithmically or mechanically determine when the third smart contractis executed and under which terms, listed in the authorship metadata.

It should be understood by one having ordinary skill in the art that theuse of a first, second, and third smart contract is exemplary and notintended to be an exhaustive manner of carrying out the method 600 inthe present disclosure. As such, one or more smart contracts may be usedto update authorship metadata stored “on-chain,” to update the relativeauthorship values in response to the change, and facilitate a royaltypayment.

In various embodiments, a performance of a work (e.g., playing orstreaming a song) that is stored in a data file may trigger royaltypayments to authors, copyright holders, etc. that are listed in theauthorship metadata associated with the performed work. For example, adigital media file may be configured to be read within an Ethereumblockchain framework. Accordingly, a stream of a song may lead to thedisbursement of royalty payments according to a set of rules,conditions, or events.

In yet other implementations, payment for the performance of a work isgating to playing or streaming a song that is stored in a digital mediafile. For example, if an entity, such as a radio station, desires toplay a song, the radio station must pay the required fee according to apay-for-play model through a personal wallet to affect a mechanicalroyalty payment.

FIG. 7 depicts stages of a method for generation and execution of asmart contract according to some embodiments of the present disclosure.FIG. 7 is a flow chart setting forth the general stages involved in amethod 700 consistent with an embodiment of the disclosure for providingauthorship platform 100. Method 700 may be implemented using a computingdevice 900 or any other component associated with platform 100 asdescribed in more detail below with respect to FIG. 9. For illustrativepurposes alone, computing device 900 is described as one potential actorin the follow stages.

Method 700 may begin at starting block and proceed to stage 710 wherecomputing device 900 may generate authorship metadata for a media file.

From stage 710, where computing device 900 generates authorshipmetadata, method 700 may advance to stage 720 where computing device 900may monitor or update the authorship metadata. For example, computingdevice 900 may update the metadata in response to the data file beingchanged. As another example, computing device 900 may monitor authorshipdata to trigger a change in the terms of a smart contract.

Once computing device 900 monitors or updates the metadata in stage 720,method 700 may continue to stage 730 where computing device 900 mayparse the metadata into terms. For example, by extracting users andauthorship values or percentages from authorship metadata.

After computing device 900 parses the metadata in stage 730, method 700may proceed to stage 740 where computing device 900 may generate adocument or documentation containing an arrangement of terms parsed fromthe metadata. For example, a metadata protocol module as disclosedherein may parse terms and provide them to a document generation module.

Once computing device 900 generates a document or documentation in stage740, method 700 may proceed to stage 750 where the document ordocumentation may be authenticated by the authentication module, such asby being processed for signature, e-signature, or other validation.

Once computing device 900 authenticates the document or documentation instage 750, the method 700 may proceed to stage 760 where a smartcontract module may generate a smart contract incorporating theauthenticated or signed document or documentation.

From stage 760 where the computing device 900 generates a smartcontract, method 700 may proceed to stage 770 where the computing device900 may monitor for generation of a royalty from the media file. Forexample, royalty events may be recorded in a datastore, local, remote,decentralized, or other. In some embodiments, such datastores may bemonitored, for example, by a network communication module as disclosedherein.

From stage 770 where the computing device 900 monitors for royaltygeneration, method 700 may proceed to stage 780 where a contract may beexecuted. For example, a smart contract may be mechanically executedaccording to terms algorithmically derived from authorship metadatahosted on a ledger or blockchain. In some embodiments, the financialtransaction module may automatically process or generate paymentsaccording to terms of the smart contract. For example, the computingdevice 900 may initiate and facilitate an electronic money transfer,printing and mailing of a check or cryptowallet, or other financialtransaction. From stage 780 where the contract is executed, method 700may end at ending block.

Referring now to FIG. 8, method 800 may begin at starting block stage810 where computing device 900 may generate a first DAW associated witha first user device. For example, the first DAW may include a personalidentification of the user of the user device and an audio data file.The personal identification may include a user's name, address, SSN, orany suitable identification that can be used to determine identity ofthe user.

From stage 810, where computing device 900 generate the first DAWassociated with the user device, method 800 may advance to stage 820where computing device 900 may receive a request from a second userdevice to access the first DAW. The request from the second user devicemay be received from an API layer of the second user device, in thecollaboration module, or from a software application running on thesecond user device's web browser.

Once computing device 900 receives the request from the second userdevice in stage 820, method 800 may continue to stage 830 wherecomputing device 900 may, upon a determination that the second useddevice is an authorized device, grant, to the second device, access tothe first DAW. The authorized second user may access a copy of the firstDAW on his local computing device (i.e., on his PC, laptop, smartphone).Alternatively, the authorized second user may access an online copy ofthe first DAW shared with him by a cloud server.

Once computing device 900 grants to the second user device access to thefirst DAW in stage 830, method 800 may continue to stage 840 wherecomputing device 900 may update the first DAW by adding anidentification of the user of the second user device.

Once computing device 900 updates the first DAW by adding theidentification of the user of the user device in stage 840, method 800may end at stage 850 where computing device 900 may generate a firstmetadata based on the first DAW. For example, the first metadataincludes a first contribution value by the user to the audio data fileand a second contribution value by the second user to the audio datafile.

FIGS. 10A-10K, are flowcharts setting forth the general stages involvedin methods 1000A-1000K consistent with embodiments of the disclosure forproviding synchronized platform 100. Methods 1000A-1000K may beimplemented using a computing device 900 or any other componentassociated with platform 100 as described in more detail below withrespect to FIG. 1 and FIG. 9. For illustrative purposes alone, computingdevice 900 is described as one potential actor in the follow stages.

Method 1000A may begin at starting stage 1002 where computing device 900may obtain a first DAW from a first user device. For example, the firstDAW may include a personal identification of the user of the user deviceand an audio data file. A DAW is a software application which users(i.e., artists, songwriters, musicians) employ to create, revise andmodify audio data files (i.e., songs, music compositions). The personalidentification may include name, address, SSN, or any suitableidentification that can be used to determine identity of the user. Thefirst DAW may be a software running and being stored on a localcomputing device (i.e., laptop, PC, smartphone, et.), or a softwarerunning online and being stored on a remote cloud server. As anotherexample, the first DAW is an application running on a web browser on theuser device.

From stage 1002, where computing device 900 obtaining the first DAW fromthe user device, method 1000A may advance to stage 1004 where computingdevice 900 may determine whether the user of the user device is anauthorized user. To that end, any suitable authorization method known inthe art can be used. If the user is determined as an unauthorized user,then the user is not allowed to access to modify or revise the first DAWand the first DAW may be discarded.

Once computing device 900 determines whether the user of the user deviceis authorized user, in stage 1004, method 1000A may continue to stage1006 where computing device 900 may generate a first metadata based onthe first DAW. For example, the first metadata includes a firstcontribution value by the user to the audio data file. A contributionvalue indicates how the user contributed to creating DAW (i.e., whatpercentage of the song is a result of his work).

As illustrated in FIG. 10B, after computing device 900 generates thefirst metadata based on the first DAW in stage 1006, method 1000B mayproceed to stage 1008 where computing device 900 may upon detecting anupdate to the first DAW, determine whether the update is performed by anauthorized user. Any suitable authorization method known in the art canbe used. If the user is determined as an unauthorized user, then updateto the first DAW is discarded.

Once computing device 900 determines whether the update is performed byan authorized user, in stage 1008, method 1000B may continue to stage1010 where computing device 900 may generate a second DAW and a secondmetadata associated with the second DAW. For example, the second DAW maybe a software running on the user device or a software running on a webbrowser on the user device. That is, the second DAW may be a softwarerunning that is stored on the local computing device, or a softwarerunning online is stored on the remote cloud server. The second DAW andits associated metadata (i.e., the second metadata) are generated basedon the first DAW.

Once computing device 900 generates the second DAW and the secondmetadata in stage 1010, method 1000B may then end at stage 1012 whereinthe computing device 900 may store the first DAW, the first metadata,the second DAW, and the second metadata.

Referring now to FIG. 10C, method 1000C may begin at starting stage 1014where computing device 900 may obtain a first DAW from a first userdevice. For example, the first DAW may include a personal identificationof the user of the user device and an audio data file. A DAW is asoftware application which users (e.g., artists, songwriters, musicians)employ to create, revise and modify audio data files (e.g., songs, musiccompositions). The personal identification may include name, address,SSN, or any suitable identification that can be used to determineidentity of the user. The first DAW may be a software running and beingstored on a local computing device (i.e., laptop, PC, smartphone, et.),or a software running online and being stored on a remote cloud server.As another example, the first DAW is an application running on a webbrowser on the user device.

From stage 1014, where computing device 900 obtains the first DAW fromthe user device, method 1000C may advance to stage 1016 where computingdevice 900 may generate a first metadata based on the first DAW. Forexample, the first metadata includes a first contribution value by theuser to the audio data file. A contribution value indicates how the usercontributed to creating DAW (i.e., what percentage of the song is aresult of his work).

Once computing device 900 generates the first metadata in stage 1016,method 1000C may continue to stage 1018 where computing device 900 maygenerate a first document based on the first DAW and the first metadata.For example, the first document may include information about copyrightsof the audio data file (i.e., copyrights information of the song). Thefirst document may be a legal document that can be used to determineeach user's copyrights and shares of royalty.

As illustrated in FIG. 10D, after computing device 900 generates thefirst document based on the first DAW and the first metadata in stage1018, method 1000D may proceed to stage 1020 where computing device 900may upon detecting an update to the first DAW, determine whether theupdate is performed by an authorized user. Any suitable authorizationmethod known in the art can be used. If the user is determined as anunauthorized user, then update to the first DAW is discarded.

Once computing device 900 determines whether the update is performed byan authorized user, in stage 1020, method 1000D may continue to stage1022 where computing device 900 may generate a second DAW and a secondmetadata associated with the second DAW. For example, the second DAW isa software running on the user device or a software running on a webbrowser on the user device. That is, the second DAW may be a softwarerunning and is stored on the local computing device, or a softwarerunning online and is stored on the remote cloud server. The second DAWand its associated metadata (i.e., the second metadata) are generatedbased on the first DAW.

Once computing device 900 generates the second DAW and the secondmetadata in stage 1022, method 1000D may continue to stage 1024 wherecomputing device 900 may generate a second document based on the secondDAW and the second metadata. For example, the second document mayinclude information about copyrights of the second DAW (i.e., copyrightsinformation of the song). The second document may be a legal documentthat can be used to determine each user's copyrights and shares ofroyalty.

Once computing device 900 generates the second document in stage 1024,method 1000D may then end at stage 1026 wherein the computing device 900may store the first DAW, the first metadata, the second DAW, the secondmetadata, the first document, and the second document.

Referring now to FIG. 10E, method 1000E may begin at starting stage 1028where computing device 900 may obtain a first DAW from a first userdevice. For example, the first DAW may include a personal identificationof the user of the user device and an audio data file. A DAW is asoftware application which users (e.g., artists, songwriters, musicians)employ to create, revise and modify audio data files (e.g., songs, musiccompositions). The first DAW may be shared by two or more user device.The personal identification may include name, address, SSN, or anysuitable identification that can be used to determine identity of theuser. The first DAW may be a software running that is being stored on alocal computing device (i.e., laptop, PC, smartphone, et.), or asoftware running online that is stored on a remote cloud server. Asanother example, the first DAW is an application running on a webbrowser on the user device.

From stage 1028, where computing device 900 obtains the first DAW fromthe user device, method 1000E may advance to stage 1030 where computingdevice 900 may generate a first metadata based on the first DAW. Forexample, the first metadata includes a first contribution value by theuser to the audio data file. A contribution value indicates how the usercontributed to the song (e.g., what percentage of the song is a resultof his work).

Once computing device 900 generates the first metadata in stage 1030,method 1000E may continue to stage 1032 where computing device 900 maycalculate a share for the user based on a number of times the audio datafile (i.e., the song) is streamed or played and the first contributionvalue by the user to the audio data file.

Once computing device 900 calculates a share for the user in stage 1032,method 1000E may continue to stage 1034 where computing device 900 maygenerate a first ledger for the first DAW based on the calculated share.For example, the first ledger may include a data file includinginformation about royalties measured based on the number of times thesong is streamed or played. The user's share of royalty can becalculated and stored on the first ledger.

Referring to FIG. 10F, method 1000F may begin at starting stage 1036where computing device 900 may, upon detecting an update to the numberof times the song is streamed or played, generate a second ledger basedon the update to the number of times the audio data file is streamed orplayed.

Once computing device 900 generates the second ledger in stage 1036,method 1000F may then end at stage 1038 where computing device 900 maystore the second ledger.

Referring to FIG. 10G, method 1000G may begin at starting stage 1040where computing device 900 may upon a determination that the user of theuser device is an authorized user, enable the user to update the firstDAW. Any suitable authorization method known in the art can be used. Ifthe user is determined as an unauthorized user, then update to the firstDAW is discarded.

Once computing device 900 enables the user to update the first DAW instage 1040, method 1000G may continue to stage 1042 where computingdevice 900 may generate a second metadata based on the updated DAW. Forexample, the second metadata includes a second contribution value by theuser to the audio data file.

Once computing device 900 generates the second metadata in stage 1042,method 1000G may continue to stage 1044 where computing device 900 maygenerate a second ledger based on the updated DAW and the secondmetadata. For example, the second ledger may include a data fileincluding information about royalties measured based on the updated DAW.The user's share of royalty can be calculated and stored on the secondledger.

Once computing device 900 generates the second ledger in stage 1044,method 1000G may then end at stage 1046 wherein the computing device 900may store the first DAW, the first metadata, the updated DAW, the secondmetadata, the first ledger, and the second ledger. For example, thefirst DAW, the first metadata, the updated DAW, and the second metadatacan be retrieved from either first ledger or the second ledger.

Referring now to FIG. 10H, method 1000H may begin at starting blockstage 1048 where computing device 900 may generate a first DAWassociated with a first user device. For example, the first DAW mayinclude a personal identification of the user of the user device and anaudio data file. A DAW is a software application which users (i.e.,artists, songwriters, musicians) employ to create, revise and modifyaudio data files (i.e., songs, music compositions). The personalidentification may include name, address, SSN, or any suitableidentification that can be used to determine identity of the user. Thefirst DAW may be a software running and being stored on a localcomputing device (i.e., laptop, PC, smartphone, etc.), or a softwarerunning online and being stored on a remote cloud server. As anotherexample, the first DAW is an application running on a web browser on theuser device.

From stage 1048, where computing device 900 generate the first DAWassociated with the user device, method 1000H may advance to stage 1050where computing device 900 may receive a request from a second userdevice to access the first DAW. The request from the second user devicemay be received from an API layer of the second user device, or from anapplication running on second user device's web browser.

Once computing device 900 receives the request from the second userdevice in stage 1050, method 1000H may continue to stage 1052 wherecomputing device 900 may, upon a determination that the second useddevice is an authorized device, grant, to the second device, access tothe first DAW. The authorized second user may access a copy of the firstDAW on his local computing device (i.e., on his PC, laptop, smartphone).Alternatively, the authorized second user may access an online copy ofthe first DAW shared with him by a cloud server.

Once computing device 900 grants to the second user device access to thefirst DAW in stage 1052, method 1000H may continue to stage 1054 wherecomputing device 900 may update the first DAW by adding anidentification of the user of the second user device. The personalidentification may include name, address, SSN, or any suitableidentification that can be used to determine identity of the user of thesecond user device.

Once computing device 900 updates the first DAW by adding theidentification of the user of the user device in stage 1054, method1000H may end at stage 1056 where computing device 900 may generate afirst metadata based on the first DAW. For example, the first metadataincludes a first contribution value by the user to the audio data fileand a second contribution value by the second user to the audio datafile. A contribution value indicates how the user contributed tocreating DAW (i.e., what percentage of the song is a result of hiswork).

Referring now to FIG. 10I, method 1000I may begin at starting stage 1058where computing device 900 may, upon detecting an update to the firstDAW by the first user or the second user, generates a second metadataand a second DAW based on the update to the first DAW. For example, thesecond metadata includes an updated contribution value by the first userto the audio data file and an update contribution value by the seconduser to the audio data file. This ensures that while the users areupdating the DAW (i.e., while the songwriters are modifying the song),DAW and its associated metadata including each user's contribution isconstantly updated to reflect the most recent DAW and contributionvalues.

Once computing device 900 generates the second metadata in stage 1058,method 1000I may then end at stage 1060 wherein the computing device 900may store the first DAW, the first metadata, the second DAW, and thesecond metadata. For example, the first DAW is stored locally on thefirst user device. For example, the second DAW is stored remotely on acloud server and is shared with the authorized user's user devices. Insome embodiments, generating the second DAW and the second metadata areperformed in real-time. In some embodiments, the first DAW and thesecond DAW are in communication with each other. The communication maybe in real-time or at pre-defined time intervals. (i.e., each 10seconds, each 1 minute, every hour, every other day, etc.).

Referring now to FIG. 10I, method 1000I may begin at starting stage 1062where computing device 900 may obtain a first DAW. For example, thefirst DAW may include a personal identification of each user of the userdevice and an audio data file. A DAW is a software application whichusers (i.e., artists, songwriters, musicians) employ to create, reviseand modify audio data files (i.e., songs, music compositions). Thepersonal identification may include name, address, SSN, or any suitableidentification that can be used to determine identity of the user. Thefirst DAW may be a software running and being stored on a localcomputing device (i.e., laptop, PC, smartphone, et.), or a softwarerunning online and being stored on a remote cloud server. As anotherexample, the first DAW is an application running on a web browser on theuser device.

From stage 1062, where computing device 900 obtains the first DAW,method 1000I may advance to stage 1064 where computing device 900 maygenerate a first metadata based on the first DAW. For example, the firstmetadata includes a first contribution value by the user of each userdevice to the audio data file. A contribution value indicates how theuser contributed to the song (e.g., what percentage of the song is aresult of his work).

Once computing device 900 generates the first metadata in stage 1064,method 1000I may end at stage 1066 where computing device 900 maycalculate a share for each user based on a number of times the audiodata file (i.e., the song) is streamed or played and the firstcontribution value by each user to the audio data file.

Referring to FIG. 10K now, method 1000K may begin at starting stage 1068where computing device 900 may, upon detecting an update to the numberof times the audio data file is streamed or played, recalculate, foruser of each user device, the share based on the update to the number oftimes the audio data file is streamed or played and the firstcontribution value associated with the user.

Once computing device 900 re-calculates a share for each user in stage1068, method 1000K may end at stage 1070 where computing device 900 maystore the first DAW, the first metadata, the calculated share for eachuser, and the re-calculated share for each user.

B. Computing System

Embodiments of the present disclosure provide a hardware and softwareplatform operative as a distributed system of modules and computingelements.

Platform 100 may be embodied as, for example, but not be limited to, awebsite, a web application, a desktop application, backend application,and a mobile application compatible with a computing device 900. Thecomputing device 900 may comprise, but not be limited to the following:

Mobile computing device, such as, but is not limited to, a laptop, atablet, a smartphone, a drone, a wearable, an embedded device, ahandheld device, an Arduino, an industrial device, or a remotelyoperable recording device;

A supercomputer, an exa-scale supercomputer, a mainframe, or a quantumcomputer;

A minicomputer, wherein the minicomputer computing device comprises, butis not limited to, an IBM AS400/iSeries/System I, A DEC VAX/PDP, aHP3000, a Honeywell-Bull DPS, a Texas Instruments TI-990, or a WangLaboratories VS Series;

A microcomputer, wherein the microcomputer computing device comprises,but is not limited to, a server, wherein a server may be rack mounted, aworkstation, an industrial device, a raspberry pi, a desktop, or anembedded device;

Platform 100 may be hosted on a centralized server or a cloud computingservice. Although the methods disclosed herein have been sometimesdescribed to be performed by a computing device 900, it should beunderstood that, in some embodiments, different operations may beperformed by a plurality of the computing devices 900 in operativecommunication at least one network.

Embodiments of the present disclosure may comprise a system having acentral processing unit (CPU) 920, a bus 930, a memory unit 940, a powersupply unit (PSU) 950, and one or more Input/Output (I/O) units. The CPU920 coupled to the memory unit 940 and the plurality of I/O units 960via the bus 930, all of which are powered by the PSU 950. It should beunderstood that, in some embodiments, each disclosed unit may actuallybe a plurality of such units for the purposes of redundancy, highavailability, and/or performance. The combination of the presentlydisclosed units is configured to perform the stages any method disclosedherein.

FIG. 9 is a block diagram of a system including computing device 900.Consistent with an embodiment of the disclosure, the aforementioned CPU920, the bus 930, the memory unit 940, a PSU 950, and the plurality ofI/O units 960 may be implemented in a computing device, such ascomputing device 900 of FIG. 9. Any suitable combination of hardware,software, or firmware may be used to implement the aforementioned units.For example, the CPU 920, the bus 930, and the memory unit 940 may beimplemented with computing device 900 or any of other computing devices900, in combination with computing device 900. The aforementionedsystem, device, and components are examples and other systems, devices,and components may comprise the aforementioned CPU 920, the bus 930, thememory unit 940, consistent with embodiments of the disclosure.

At least one computing device 900 may be embodied as any of thecomputing elements illustrated in all of the attached figures,including; A Network Layer, An Authorship/Collaboration Platform Layer,A DAW/Media Layer, A Datastore Layer, An External Device Layer, anAccount Layer, A Decentralized Exchange Layer, a Metadata ProtocolModule, a Blockchain Protocol Module, A Network Communication Module, aDocument Generation Module, A Contract Generation Module, AnAuthentication Module, A Financial Transaction Module, A CollaborationModule, A Resource Management Module, A Software Integration Module, amethods for attributing authorship, methods for generating a document,methods for reading/writing/monitoring data or metadata stored on aledger or blockchain, methods facilitating or enabling collaborativedigital media authorship or production, and methods for automatic,mechanical royalty calculation and disbursement. A computing device 900does not need to be electronic, nor even have a CPU 920, nor bus 930,nor memory unit 940. The definition of the computing device 900 to aperson having ordinary skill in the art is a device that computes,especially a programmable [usually] electronic machine that performshigh-speed mathematical or logical operations or that assembles, stores,correlates, or otherwise processes information. Any device whichprocesses information qualifies as a computing device 900, especially ifthe processing is purposeful.

With reference to FIG. 9, a system consistent with an embodiment of thedisclosure may include a computing device, such as computing device 900.In a basic configuration, computing device 900 may include at least oneclock module 910, at least one CPU 920, at least one bus 930, and atleast one memory unit 940, at least one PSU 950, and at least one I/O960 module, wherein I/O module may be comprised of, but not limited to anon-volatile storage sub-module 961, a communication sub-module 962, asensors sub-module 963, and a peripherals sub-module 964.

A system consistent with an embodiment of the disclosure the computingdevice 900 may include the clock module 910 may be known to a personhaving ordinary skill in the art as a clock generator, which producesclock signals. Clock signal is a particular type of signal thatoscillates between a high and a low state and is used like a metronometo coordinate actions of digital circuits. Most integrated circuits(ICs) of sufficient complexity use a clock signal in order tosynchronize different parts of the circuit, cycling ata rate slower thanthe worst-case internal propagation delays. The preeminent example ofthe aforementioned integrated circuit is the CPU 920, the centralcomponent of modern computers, which relies on a clock. The onlyexceptions are asynchronous circuits such as asynchronous CPUs. Theclock 910 can comprise a plurality of embodiments, such as, but notlimited to, single-phase clock which transmits all clock signals oneffectively 1 wire, two-phase clock which distributes clock signals ontwo wires, each with non-overlapping pulses, and four-phase clock whichdistributes clock signals on 4 wires.

Many computing devices 900 use a “clock multiplier” which multiplies alower frequency external clock to the appropriate clock rate of the CPU920. This allows the CPU 920 to operate at a much higher frequency thanthe rest of the computer, which affords performance gains in situationswhere the CPU 920 does not need to wait on an external factor (likememory 940 or input/output 960). Some embodiments of the clock 910 mayinclude dynamic frequency change, where, the time between clock edgescan vary widely from one edge to the next and back again.

A system consistent with an embodiment of the disclosure the computingdevice 900 may include the CPU unit 820 comprising at least one CPU Core921. A plurality of CPU cores 921 may comprise identical CPU cores 921,such as, but not limited to, homogeneous multi-core systems. It is alsopossible for the plurality of CPU cores 921 to comprise different CPUcores 921, such as, but not limited to, heterogeneous multi-coresystems, big.LITTLE systems and some AMD accelerated processing units(APU). The CPU unit 920 reads and executes program instructions whichmay be used across many application domains, for example, but notlimited to, general purpose computing, embedded computing, networkcomputing, digital signal processing (DSP), and graphics processing(GPU). The CPU unit 920 may run multiple instructions on separate CPUcores 921 at the same time. The CPU unit 920 may be integrated into atleast one of a single integrated circuit die and multiple dies in asingle chip package. The single integrated circuit die and multiple diesin a single chip package may contain a plurality of other aspects of thecomputing device 900, for example, but not limited to, the clock 910,the CPU 920, the bus 930, the memory 940, and I/O 960.

The CPU unit 920 may contain cache 922 such as, but not limited to, alevel 1 cache, level 2 cache, level 3 cache or combination thereof. Theaforementioned cache 922 may or may not be shared amongst a plurality ofCPU cores 921. The cache 922 sharing comprises at least one of messagepassing and inter-core communication methods may be used for the atleast one CPU Core 921 to communicate with the cache 922. The inter-corecommunication methods may comprise, but not limited to, bus, ring,two-dimensional mesh, and crossbar. The aforementioned CPU unit 920 mayemploy symmetric multiprocessing (SMP) design.

The plurality of the aforementioned CPU cores 921 may comprise softmicroprocessor cores on a single field programmable gate array (FPGA),such as semiconductor intellectual property cores (IP Core). Theplurality of CPU cores 921 architecture may be based on at least one of,but not limited to, Complex instruction set computing (CISC), Zeroinstruction set computing (ZISC), and Reduced instruction set computing(RISC). At least one of the performance-enhancing methods may beemployed by the plurality of the CPU cores 921, for example, but notlimited to Instruction-level parallelism (ILP) such as, but not limitedto, superscalar pipelining, and Thread-level parallelism (TLP).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 900 may employ a communication systemthat transfers data between components inside the aforementionedcomputing device 900, and/or the plurality of computing devices 900. Theaforementioned communication system will be known to a person havingordinary skill in the art as a bus 930. The bus 930 may embody internaland/or external plurality of hardware and software components, forexample, but not limited to a wire, optical fiber, communicationprotocols, and any physical arrangement that provides the same logicalfunction as a parallel electrical bus. The bus 930 may comprise at leastone of, but not limited to a parallel bus, wherein the parallel buscarry data words in parallel on multiple wires, and a serial bus,wherein the serial bus carry data in bit-serial form. The bus 930 mayembody a plurality of topologies, for example, but not limited to, amultidrop/electrical parallel topology, a daisy chain topology, and aconnected by switched hubs, such as USB bus. The bus 930 may comprise aplurality of embodiments, for example, but not limited to:

-   -   Internal data bus (data bus) 931/Memory bus    -   Control bus 932    -   Address bus 933    -   System Management Bus (SMBus)    -   Front-Side-Bus (FSB)    -   External Bus Interface (EBI)    -   Local bus    -   Expansion bus    -   Lightning bus    -   Controller Area Network (CAN bus)    -   Camera Link    -   ExpressCard    -   Advanced Technology management Attachment (ATA), including        embodiments and derivatives such as, but not limited to,        Integrated Drive Electronics (IDE)/Enhanced IDE (EIDE), ATA        Packet Interface (ATAPI), Ultra-Direct Memory Access (UDMA),        Ultra ATA (UATA)/Parallel ATA (PATA)/Serial ATA (SATA),        CompactFlash (CF) interface, Consumer Electronics ATA        (CE-ATA)/Fiber Attached Technology Adapted (FATA), Advanced Host        Controller Interface (AHCI), SATA Express (SATAe)/External SATA        (eSATA), including the powered embodiment eSATAp/Mini-SATA        (mSATA), and Next Generation Form Factor (NGFF)/M.2.    -   Small Computer System Interface (SCSI)/Serial Attached SCSI        (SAS)    -   HyperTransport    -   InfiniBand    -   RapidIO    -   Mobile Industry Processor Interface (MIPI)    -   Coherent Processor Interface (CAPI)    -   Plug-n-play    -   1-Wire    -   Peripheral Component Interconnect (PCI), including embodiments        such as, but not limited to, Accelerated Graphics Port (AGP),        Peripheral Component Interconnect eXtended (PCI-X), Peripheral        Component Interconnect Express (PCI-e) (e.g., PCI Express Mini        Card, PCI Express M.2 [Mini PCIe v2], PCI Express External        Cabling [ePCIe], and PCI Express OCuLink [Optical Copper{Cu}        Link]), Express Card, AdvancedTCA, AMC, Universal IO,        Thunderbolt/Mini DisplayPort, Mobile PCIe (M-PCIe), U.2, and        Non-Volatile Memory Express (NVMe)/Non-Volatile Memory Host        Controller Interface Specification (NVMHCIS).    -   Industry Standard Architecture (ISA), including embodiments such        as, but not limited to Extended ISA (EISA),        PC/XT-bus/PC/AT-bus/PC/104 bus (e.g., PC/104-Plus,        PCI/104-Express, PCI/104, and PCI-104), and Low Pin Count (LPC).    -   Music Instrument Digital Interface (MIDI)    -   Universal Serial Bus (USB), including embodiments such as, but        not limited to, Media Transfer Protocol (MTP)/Mobile        High-Definition Link (MHL), Device Firmware Upgrade (DFU),        wireless USB, InterChip USB, IEEE 1394 Interface/Firewire,        Thunderbolt, and eXtensible Host Controller Interface (xHCI).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 900 may employ hardware integratedcircuits that store information for immediate use in the computingdevice 900, know to the person having ordinary skill in the art asprimary storage or memory 940. The memory 940 operates at high speed,distinguishing it from the non-volatile storage sub-module 961, whichmay be referred to as secondary or tertiary storage, which providesslow-to-access information but offers higher capacities at lower cost.The contents contained in memory 940, may be transferred to secondarystorage via techniques such as, but not limited to, virtual memory andswap. The memory 940 may be associated with addressable semiconductormemory, such as integrated circuits consisting of silicon-basedtransistors, used for example as primary storage but also other purposesin the computing device 900. The memory 940 may comprise a plurality ofembodiments, such as, but not limited to volatile memory, non-volatilememory, and semi-volatile memory. It should be understood by a personhaving ordinary skill in the art that the ensuing are non-limitingexamples of the aforementioned memory:

-   -   Volatile memory which requires power to maintain stored        information, for example, but not limited to, Dynamic        Random-Access Memory (DRAM) 941, Static Random-Access Memory        (SRAM) 942, CPU Cache memory 925, Advanced Random-Access Memory        (A-RAM), and other types of primary storage such as        Random-Access Memory (RAM).    -   Non-volatile memory which can retain stored information even        after power is removed, for example, but not limited to,        Read-Only Memory (ROM) 943, Programmable ROM (PROM) 944,        Erasable PROM (EPROM) 945, Electrically Erasable PROM (EEPROM)        946 (e.g., flash memory and Electrically Alterable PROM        [EAPROM]), Mask ROM (MROM), One Time Programable (OTP) ROM/Write        Once Read Many (WORM), Ferroelectric RAM (FeRAM), Parallel        Random-Access Machine (PRAM), Split-Transfer Torque RAM        (STT-RAM), Silicon Oxime Nitride Oxide Silicon (SONOS),        Resistive RAM (RRAM), Nano RAM (NRAM), 3D XPoint, Domain-Wall        Memory (DWM), and millipede memory.    -   Semi-volatile memory which may have some limited non-volatile        duration after power is removed but loses data after said        duration has passed. Semi-volatile memory provides high        performance, durability, and other valuable characteristics        typically associated with volatile memory, while providing some        benefits of true non-volatile memory. The semi-volatile memory        may comprise volatile and non-volatile memory and/or volatile        memory with battery to provide power after power is removed. The        semi-volatile memory may comprise, but not limited to        spin-transfer torque RAM (STT-RAM).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 900 may employ the communication systembetween an information processing system, such as the computing device900, and the outside world, for example, but not limited to, human,environment, and another computing device 900. The aforementionedcommunication system will be known to a person having ordinary skill inthe art as I/O 960. The I/O module 960 regulates a plurality of inputsand outputs with regard to the computing device 900, wherein the inputsare a plurality of signals and data received by the computing device900, and the outputs are the plurality of signals and data sent from thecomputing device 900. The I/O module 960 interfaces a plurality ofhardware, such as, but not limited to, non-volatile storage 961,communication devices 962, sensors 963, and peripherals 964. Theplurality of hardware is used by the at least one of, but not limitedto, human, environment, and another computing device 900 to communicatewith the present computing device 900. The I/O module 960 may comprise aplurality of forms, for example, but not limited to channel I/O, portmapped I/O, asynchronous I/O, and Direct Memory Access (DMA).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 900 may employ the non-volatile storagesub-module 961, which may be referred to by a person having ordinaryskill in the art as one of secondary storage, external memory, tertiarystorage, off-line storage, and auxiliary storage. The non-volatilestorage sub-module 961 may not be accessed directly by the CPU 920without using intermediate area in the memory 940. The non-volatilestorage sub-module 961 does not lose data when power is removed and maybe two orders of magnitude less costly than storage used in memorymodule, at the expense of speed and latency. The non-volatile storagesub-module 861 may comprise a plurality of forms, such as, but notlimited to, Direct Attached Storage (DAS), Network Attached Storage(NAS), Storage Area Network (SAN), nearline storage, Massive Array ofIdle Disks (MAID), Redundant Array of Independent Disks (RAID), devicemirroring, off-line storage, and robotic storage. The non-volatilestorage sub-module (961) may comprise a plurality of embodiments, suchas, but not limited to:

-   -   Optical storage, for example, but not limited to, Compact        Disk (CD) (CD-ROM/CD-R/CD-RW), Digital Versatile Disk (DVD)        (DVD-ROM/DVD-R/DVD+R/DVD-RW/DVD+RW/DVD±RW/DVD+R        DL/DVD-RAM/HD-DVD), Blu-ray Disk (BD) (BD-ROM/BD-R/BD-RE/BD-R        DL/BD-RE DL), and Ultra-Density Optical (UDO).    -   Semiconductor storage, for example, but not limited to, flash        memory, such as, but not limited to, USB flash drive, Memory        card, Subscriber Identity Module (SIM) card, Secure Digital (SD)        card, Smart Card, CompactFlash (CF) card, Solid-State Drive        (SSD) and memristor.    -   Magnetic storage such as, but not limited to, Hard Disk Drive        (HDD), tape drive, carousel memory, and Card Random-Access        Memory (CRAM).    -   Phase-change memory    -   Holographic data storage such as Holographic Versatile Disk        (HVD).    -   Molecular Memory    -   Deoxyribonucleic Acid (DNA) digital data storage

Consistent with the embodiments of the present disclosure, theaforementioned computing device 900 may employ the communicationsub-module 962 as a subset of the I/O 960, which may be referred to by aperson having ordinary skill in the art as at least one of, but notlimited to, computer network, data network, and network. The networkallows computing devices 900 to exchange data using connections, whichmay be known to a person having ordinary skill in the art as data links,between network nodes. The nodes comprise network computer devices 900that originate, route, and terminate data. The nodes are identified bynetwork addresses and can include a plurality of hosts consistent withthe embodiments of a computing device 900. The aforementionedembodiments include, but not limited to personal computers, phones,servers, drones, and networking devices such as, but not limited to,hubs, switches, routers, modems, and firewalls.

Two nodes can be said are networked together, when one computing device900 is able to exchange information with the other computing device 900,whether or not they have a direct connection with each other. Thecommunication sub-module 962 supports a plurality of applications andservices, such as, but not limited to World Wide Web (WWW), digitalvideo and audio, shared use of application and storage computing devices900, printers/scanners/fax machines, email/online chat/instantmessaging, remote control, distributed computing, etc. The network maycomprise a plurality of transmission mediums, such as, but not limitedto conductive wire, fiber optics, and wireless. The network may comprisea plurality of communications protocols to organize network traffic,wherein application-specific communications protocols are layered, maybe known to a person having ordinary skill in the art as carried aspayload, over other more general communications protocols. The pluralityof communications protocols may comprise, but not limited to, IEEE 802,ethernet, Wireless LAN (WLAN/Wi-Fi), Internet Protocol (IP) suite (e.g.,TCP/IP, UDP, Internet Protocol version 4 [IPv4], and Internet Protocolversion 6 [IPv6]), Synchronous Optical Networking (SONET)/SynchronousDigital Hierarchy (SDH), Asynchronous Transfer Mode (ATM), and cellularstandards (e.g., Global System for Mobile Communications [GSM], GeneralPacket Radio Service [GPRS], Code-Division Multiple Access [CDMA], andIntegrated Digital Enhanced Network [IDEN]).

The communication sub-module 862 may comprise a plurality of size,topology, traffic control mechanism and organizational intent. Thecommunication sub-module 962 may comprise a plurality of embodiments,such as, but not limited to:

-   -   Wired communications, such as, but not limited to, coaxial        cable, phone lines, twisted pair cables (ethernet), and        InfiniBand.    -   Wireless communications, such as, but not limited to,        communications satellites, cellular systems, radio        frequency/spread spectrum technologies, IEEE 802.11 Wi-Fi,        Bluetooth, NFC, free-space optical communications, terrestrial        microwave, and Infrared (IR) communications. Wherein cellular        systems embody technologies such as, but not limited to, 3G, 4G        (such as WiMax and LTE), and 5G (short and long wavelength).    -   Parallel communications, such as, but not limited to, LPT ports.    -   Serial communications, such as, but not limited to, RS-232 and        USB.    -   Fiber Optic communications, such as, but not limited to,        Single-mode optical fiber (SMF) and Multi-mode optical fiber        (MMF).    -   Power Line communications

The aforementioned network may comprise a plurality of layouts, such as,but not limited to, bus network such as ethernet, star network such asWi-Fi, ring network, mesh network, fully connected network, and treenetwork. The network can be characterized by its physical capacity orits organizational purpose. Use of the network, including userauthorization and access rights, differ accordingly. Thecharacterization may include, but not limited to nanoscale network,Personal Area Network (PAN), Local Area Network (LAN), Home Area Network(HAN), Storage Area Network (SAN), Campus Area Network (CAN), backbonenetwork, Metropolitan Area Network (MAN), Wide Area Network (WAN),enterprise private network, Virtual Private Network (VPN), and GlobalArea Network (GAN).

Consistent with the embodiments of the present disclosure, theaforementioned computing device 900 may employ the sensors sub-module963 as a subset of the I/O 960. The sensors sub-module 963 comprises atleast one of the devices, modules, and subsystems whose purpose is todetect events or changes in its environment and send the information tothe computing device 900. Sensors are sensitive to the measuredproperty, are not sensitive to any property not measured, but may beencountered in its application, and do not significantly influence themeasured property. The sensors sub-module 963 may comprise a pluralityof digital devices and analog devices, wherein if an analog device isused, an Analog to Digital (A-to-D) converter must be employed tointerface the said device with the computing device 900. The sensors maybe subject to a plurality of deviations that limit sensor accuracy. Thesensors sub-module 963 may comprise a plurality of embodiments, such as,but not limited to, chemical sensors, automotive sensors,acoustic/sound/vibration sensors, electric current/electricpotential/magnetic/radio sensors,environmental/weather/moisture/humidity sensors, flow/fluid velocitysensors, ionizing radiation/particle sensors, navigation sensors,position/angle/displacement/distance/speed/acceleration sensors,imaging/optical/light sensors, pressure sensors, force/density/levelsensors, thermal/temperature sensors, and proximity/presence sensors. Itshould be understood by a person having ordinary skill in the art thatthe ensuing are non-limiting examples of the aforementioned sensors:

-   -   Chemical sensors, such as, but not limited to, breathalyzer,        carbon dioxide sensor, carbon monoxide/smoke detector, catalytic        bead sensor, chemical field-effect transistor, chemiresistor,        electrochemical gas sensor, electronic nose,        electrolyte-insulator-semiconductor sensor, energy-dispersive        X-ray spectroscopy, fluorescent chloride sensors, holographic        sensor, hydrocarbon dew point analyzer, hydrogen sensor,        hydrogen sulfide sensor, infrared point sensor, ion-selective        electrode, nondispersive infrared sensor, microwave chemistry        sensor, nitrogen oxide sensor, olfactometer, optode, oxygen        sensor, ozone monitor, pellistor, pH glass electrode,        potentiometric sensor, redox electrode, zinc oxide nanorod        sensor, and biosensors (such as nanosensors).    -   Automotive sensors, such as, but not limited to, air flow        meter/mass airflow sensor, air-fuel ratio meter, AFR sensor,        blind spot monitor, engine coolant/exhaust gas/cylinder        head/transmission fluid temperature sensor, hall effect sensor,        wheel/automatic transmission/turbine/vehicle speed sensor,        airbag sensors, brake fluid/engine crankcase/fuel/oil/tire        pressure sensor, camshaft/crankshaft/throttle position sensor,        fuel/oil level sensor, knock sensor, light sensor, MAP sensor,        oxygen sensor (02), parking sensor, radar sensor, torque sensor,        variable reluctance sensor, and water-in-fuel sensor.    -   Acoustic, sound and vibration sensors, such as, but not limited        to, microphone, lace sensor (guitar pickup), seismometer, sound        locator, geophone, and hydrophone.    -   Electric current, electric potential, magnetic, and radio        sensors, such as, but not limited to, current sensor, Daly        detector, electroscope, electron multiplier, faraday cup,        galvanometer, hall effect sensor, hall probe, magnetic anomaly        detector, magnetometer, magnetoresistance, MEMS magnetic field        sensor, metal detector, planar hall sensor, radio direction        finder, and voltage detector.    -   Environmental, weather, moisture, and humidity sensors, such as,        but not limited to, actinometer, air pollution sensor,        bedwetting alarm, ceilometer, dew warning, electrochemical gas        sensor, fish counter, frequency domain sensor, gas detector,        hook gauge evaporimeter, humistor, hygrometer, leaf sensor,        lysimeter, pyranometer, pyrgeometer, psychrometer, rain gauge,        rain sensor, seismometers, SNOTEL, snow gauge, soil moisture        sensor, stream gauge, and tide gauge.    -   Flow and fluid velocity sensors, such as, but not limited to,        air flow meter, anemometer, flow sensor, gas meter, mass flow        sensor, and water meter.    -   Ionizing radiation and particle sensors, such as, but not        limited to, cloud chamber, Geiger counter, Geiger-Muller tube,        ionization chamber, neutron detection, proportional counter,        scintillation counter, semiconductor detector, and        thermoluminescent dosimeter.    -   Navigation sensors, such as, but not limited to, air speed        indicator, altimeter, attitude indicator, depth gauge, fluxgate        compass, gyroscope, inertial navigation system, inertial        reference unit, magnetic compass, MHD sensor, ring laser        gyroscope, turn coordinator, variometer, vibrating structure        gyroscope, and yaw rate sensor.    -   Position, angle, displacement, distance, speed, and acceleration        sensors, such as, but not limited to, accelerometer,        displacement sensor, flex sensor, free fall sensor, gravimeter,        impact sensor, laser rangefinder, LIDAR, odometer, photoelectric        sensor, position sensor such as, but not limited to, GPS or        Glonass, angular rate sensor, shock detector, ultrasonic sensor,        tilt sensor, tachometer, ultra-wideband radar, variable        reluctance sensor, and velocity receiver.    -   Imaging, optical and light sensors, such as, but not limited to,        CMOS sensor, colorimeter, contact image sensor, electro-optical        sensor, infra-red sensor, kinetic inductance detector, LED as        light sensor, light-addressable potentiometric sensor, Nichols        radiometer, fiber-optic sensors, optical position sensor,        thermopile laser sensor, photodetector, photodiode,        photomultiplier tubes, phototransistor, photoelectric sensor,        photoionization detector, photomultiplier, photoresistor,        photoswitch, phototube, scintillometer, Shack-Hartmann,        single-photon avalanche diode, superconducting nanowire        single-photon detector, transition edge sensor, visible light        photon counter, and wavefront sensor.    -   Pressure sensors, such as, but not limited to, barograph,        barometer, boost gauge, bourdon gauge, hot filament ionization        gauge, ionization gauge, McLeod gauge, Oscillating U-tube,        permanent downhole gauge, piezometer, Pirani gauge, pressure        sensor, pressure gauge, tactile sensor, and time pressure gauge.    -   Force, Density, and Level sensors, such as, but not limited to,        bhangmeter, hydrometer, force gauge or force sensor, level        sensor, load cell, magnetic level or nuclear density sensor or        strain gauge, piezocapacitive pressure sensor, piezoelectric        sensor, torque sensor, and viscometer.    -   Thermal and temperature sensors, such as, but not limited to,        bolometer, bimetallic strip, calorimeter, exhaust gas        temperature gauge, flame detection/pyrometer, Gardon gauge,        Golay cell, heat flux sensor, microbolometer, microwave        radiometer, net radiometer, infrared/quartz/resistance        thermometer, silicon bandgap temperature sensor, thermistor, and        thermocouple.    -   Proximity and presence sensors, such as, but not limited to,        alarm sensor, doppler radar, motion detector, occupancy sensor,        proximity sensor, passive infrared sensor, reed switch, stud        finder, triangulation sensor, touch switch, and wired glove.

Consistent with the embodiments of the present disclosure, theaforementioned computing device 900 may employ the peripheralssub-module 962 as a subset of the I/O 960. The peripheral sub-module 964comprises ancillary devices uses to put information into and getinformation out of the computing device 900. There are 3 categories ofdevices comprising the peripheral sub-module 964, which exist based ontheir relationship with the computing device 900, input devices, outputdevices, and input/output devices. Input devices send at least one ofdata and instructions to the computing device 900. Input devices can becategorized based on, but not limited to:

-   -   Modality of input, such as, but not limited to, mechanical        motion, audio, visual, and tactile.    -   Whether the input is discrete, such as but not limited to,        pressing a key, or continuous such as, but not limited to        position of a mouse.    -   The number of degrees of freedom involved, such as, but not        limited to, two-dimensional mice vs three-dimensional mice used        for Computer-Aided Design (CAD) applications.

Output devices provide output from the computing device 900. Outputdevices convert electronically generated information into a form thatcan be presented to humans. Input/output devices perform that performboth input and output functions. It should be understood by a personhaving ordinary skill in the art that the ensuing are non-limitingembodiments of the aforementioned peripheral sub-module 964:

-   -   Input Devices        -   Human Interface Devices (HID), such as, but not limited to,            pointing device (e.g., mouse, touchpad, joystick,            touchscreen, game controller/gamepad, remote, light pen,            light gun, Wii remote, jog dial, shuttle, and knob),            keyboard, graphics tablet, digital pen, gesture recognition            devices, magnetic ink character recognition, Sip-and-Puff            (SNP) device, and Language Acquisition Device (LAD).        -   High degree of freedom devices, that require up to six            degrees of freedom such as, but not limited to, camera            gimbals, Cave Automatic Virtual Environment (CAVE), and            virtual reality systems.        -   Video Input devices are used to digitize images or video            from the outside world into the computing device 900. The            information can be stored in a multitude of formats            depending on the user's requirement. Examples of types of            video input devices include, but not limited to, digital            camera, digital camcorder, portable media player, webcam,            Microsoft Kinect, image scanner, fingerprint scanner,            barcode reader, 3D scanner, laser rangefinder, eye gaze            tracker, computed tomography, magnetic resonance imaging,            positron emission tomography, medical ultrasonography, TV            tuner, and iris scanner.        -   Audio input devices are used to capture sound. In some            cases, an audio output device can be used as an input            device, in order to capture produced sound. Audio input            devices allow a user to send audio signals to the computing            device 900 for at least one of processing, recording, and            carrying out commands. Devices such as microphones allow            users to speak to the computer in order to record a voice            message or navigate software. Aside from recording, audio            input devices are also used with speech recognition            software. Examples of types of audio input devices include,            but not limited to microphone, Musical Instrumental Digital            Interface (MIDI) devices such as, but not limited to a            keyboard, and headset.        -   Data AcQuisition (DAQ) devices convert at least one of            analog signals and physical parameters to digital values for            processing by the computing device 900. Examples of DAQ            devices may include, but not limited to, Analog to Digital            Converter (ADC), data logger, signal conditioning circuitry,            multiplexer, and Time to Digital Converter (TDC).    -   Output Devices may further comprise, but not be limited to:        -   Display devices, which convert electrical information into            visual form, such as, but not limited to, monitor, TV,            projector, and Computer Output Microfilm (COM). Display            devices can use a plurality of underlying technologies, such            as, but not limited to, Cathode-Ray Tube (CRT), Thin-Film            Transistor (TFT), Liquid Crystal Display (LCD), Organic            Light-Emitting Diode (OLED), MicroLED, E Ink Display            (ePaper) and Refreshable Braille Display (Braille Terminal).        -   Printers, such as, but not limited to, inkjet printers,            laser printers, 3D printers, solid ink printers and            plotters.        -   Audio and Video (AV) devices, such as, but not limited to,            speakers, headphones, amplifiers and lights, which include            lamps, strobes, DJ lighting, stage lighting, architectural            lighting, special effect lighting, and lasers.        -   Other devices such as Digital to Analog Converter (DAC)    -   Input/Output Devices may further comprise, but not be limited        to, touchscreens, networking device (e.g., devices disclosed in        network 962 sub-module), data storage device (non-volatile        storage 961), facsimile (FAX), and graphics/sound cards.

All rights including copyrights in the code included herein are vestedin and the property of the Applicant. The Applicant retains and reservesall rights in the code included herein, and grants permission toreproduce the material only in connection with reproduction of thegranted patent and for no other purpose.

IV. Aspects

The following disclose various Aspects of the present disclosure. Thevarious Aspects are not to be construed as patent claims unless thelanguage of the Aspect appears as a patent claim. The Aspects describevarious non-limiting embodiments of the present disclosure.

First Aspect

1. A method, comprising:

generating authorship metadata for a data file;

receiving, from a first user, a first contribution to the data file, thefirst contribution comprising a change in one or more data valuesassociated with the data file;

evaluating the first contribution to produce first contribution data;and

recording the first contribution data in the authorship metadata.

2. The method of aspect 1, further comprising:

receiving, from a second user, a second contribution to the data file,the second contribution comprising a change in one or more data valuesassociated with the data file;

evaluating the second contribution to produce second contribution data;

modifying the authorship metadata based on the second contribution data;and

determining a relative authorship for the first and second user.

3. The method of aspect 1, wherein the authorship metadata is writtenonto a media file in a digital audio workstation.

4. The method of aspect 3, wherein the digital audio workstation hasinformation about the first user and is licensed to the first user.

5. The method of aspect 3, wherein the media file is a raw media file.

6. The method of aspect 1, further comprising:

receiving, from a second user, a second contribution to the data file;

evaluating the first and second contributions to produce contributiondata; and

recording the contribution data in the authorship metadata.

7. The method of aspect 1, further comprising:

receiving, from a plurality of users, a plurality of contributions tothe data file, the plurality of contributions each comprising a changein one or more data values associated with the data file;

evaluating the plurality of contributions to produce contribution datafor each contribution; and

recording the contribution data for each contribution in the authorshipmetadata.

8. The method of aspect 1, wherein the authorship metadata is recordedon a ledger.

9. The method of aspect 1, wherein the authorship metadata is recordedon a blockchain.

10. The method of aspect 1, wherein the authorship metadata is generatedwithin a digital audio workstation.

11. The method of aspect 2, wherein the authorship metadata is generatedwithin a first digital audio workstation and the authorship metadata ismodified within a second, different digital audio workstation.

12. The method of aspect 6, wherein the plurality of contributions tothe data file are made on a plurality of local digital audioworkstations.

13. The method of aspect 6, wherein the plurality of contributions tothe data file are made on a plurality of remote digital audioworkstations.

14. The method of aspect 6, wherein the plurality of contributions tothe data file are made using a plurality of different digital audioworkstations, and the method further comprises a selection from thefollowing:

reading the authorship metadata using the plurality of different digitalaudio workstations, editing the authorship metadata using the pluralityof different digital audio workstations, and changing the authorshipmetadata using the plurality of different digital audio workstations.

15. The method of aspect 1, wherein the first contribution is evaluatedin real time as the first contribution is being made to produce thefirst contribution data.

16. The method of aspect 6, wherein the plurality of contributions isevaluated using machine learning.

Second Aspect

1. A method, comprising:

receiving metadata for a data file;

parsing the metadata into terms, the terms comprising a list of usersand relative copyright ownership for each user of the list of users; and

automatically generating a legal document from the terms representingthe relative copyright ownership in the data file for each user of thelist of users.

2. The method of aspect 1, further comprising:

obtaining a signature from one or more users of the list of users.

3. The method of aspect 1, wherein the legal document is a printedcontract.

4. The method of aspect 1, wherein the legal document is embodied in asmart contract.

5. The method of aspect 4, wherein the legal document is recorded usinga ledger.

6. The method of aspect 4, wherein the legal document is recorded on ablockchain.

7. The method of aspect 3, wherein the legal document is a copyrightapplication document.

8. The method of aspect 1, further comprising:

detecting that a royalty payment associated with the data file has beenmade; and

automatically disbursing the royalty payment to each user of the list ofusers according to the relative copyright ownership represented in thelegal document.

Third Aspect

1. A method comprising:

recording one or more changes to a data file during a digital audioworkstation session;

collecting user data during the digital audio workstation session;

analyzing the user data to produce analytics;

generating documentation containing the analytics; and

storing the data file and the documentation.

2. The method of aspect 1, wherein the user data comprises a log of thechanges, the analytics contains authorship metadata for the data file,and the method further comprises analyzing the log to produce authorshipmetadata.

3. The method of aspect 1, wherein the documentation and data file aredecentrally stored.

4. The method of aspect 1, wherein the documentation and data file arestored in a ledger.

5. The method of aspect 1, wherein the documentation and data file arestored on a blockchain.

6. The method of aspect 1, wherein the digital audio workstationgenerates the documentation and stores the documentation and the datafile in one or more decentralized locations.

7. The method of aspect 1, further comprising:

changing one or more portions of a data file during a plurality ofdigital audio workstation sessions to produce a plurality of sessiondata files; and

for each digital audio workstation session of the plurality of digitalaudio workstation sessions,

collecting session user data during the digital audio workstationsession;

recording a session data file;

analyzing the session user data to produce session analytics;

generating associated session documentation containing the sessionanalytics; and

storing the session data file and associated session documentation forthe digital audio workstation session.

8. The method of aspect 7, wherein each session data file of theplurality of session data files is stored on a ledger along withmetadata associated with the session data file.

9. The method of aspect 8, wherein the metadata contains the associatedsession documentation for the session data file.

10. The method of aspect 1, further comprising:

generating a hash value for the data file; and

recording the hash value in the documentation.

11. The method of aspect 7, further comprising: for each digital audioworkstation session of the plurality of digital audio workstationsessions, generating a hash value for the session data file andrecording the hash value in the association session documentation.Fourth Aspect1. A method comprising:

running a web browser on a computing device;

operating a remote digital audio workstation using the web browser;

recording, in the remote digital audio workstation, changes to a datafile; and

recording, in the remote digital audio workstation, metadata associatedwith the data file.

2. The method of aspect 1, further comprising:

running a plurality of web browsers on a plurality of computing devices;

operating a remote digital audio workstation using the plurality of webbrowsers to make one or more changes to the data file during one or moresessions;

recording, in the remote digital audio workstation, each change of theplurality of changes to the data file; and

recording, in the remote digital audio workstation, metadata associatedwith each of the one or more sessions.

3. The method of aspect 1, wherein the remote digital audio workstationuses resources of the computing device.

4. The method of aspect 1, comprising:

operating a local digital audio workstation on the local computingdevice; and

connecting the local digital audio workstation to the remote digitalaudio workstation.

5. The method of aspect 4, comprising synchronizing, on the localdigital audio workstation and the remote digital audio workstation, aselection from the following: the data file, a history of the data file,a version value for the data file, a current metadata for the data file,a historical metadata for the data file, and authorship data for thedata file.6. The method of aspect 2, wherein the remote digital audio workstationuses resources of the plurality of computing devices.7. The method of aspect 1, wherein the metadata includes authorship datafor the data file.Fifth Aspect1. A method, comprising:

determining that a rendered media file having a plurality of authors hasgenerated a royalty, the rendered media file having associated therewithmetadata containing one or more relative authorship values for theplurality of authors; and, for each author of the plurality of authors;

identifying, from the metadata, a relative authorship value for theauthor;

determining a disbursement amount according to the relative authorshipvalue and the royalty; and

facilitating a payment of the disbursement amount to the author.

2. The method of aspect 1, wherein each author of the plurality ofauthors made a contribution to the rendered media file using a digitalaudio workstation having user information for the associated author, andwherein the user information is used to facilitate the disbursement foreach author.3. The method of aspect 2, wherein the user information comprises aselection of at least one of the following: a name, a phone number, anemail address, a physical address, a set of bank account information,and a set of other account information.4. The method of aspect 1, further comprising:

parsing, from the metadata, the authorship values; and

automatically generating an enforceable legal document apportioningcopyright ownership in the media file based on the parsed authorshipvalues.

5. The method of aspect 1, comprising receiving an agreement to a smartcontract from each author of the plurality of authors, the smartcontract agreement comprising an agreement to an apportionment ofcopyright ownership in the media file that is automatically generatedbased on authorship values parsed from the metadata.6. The method of aspect 1, further comprising:

recording a change to the rendered media file made by a first user in afirst digital audio workstation that results in a changed rendered mediafile;

evaluating the change to the rendered media file to produce firstauthorship data for the first user;

recording the first authorship data in the metadata for the changedrendered media file;

identifying, from the metadata, a first relative authorship value forthe first user;

determining a first disbursement amount for the first user according tothe first relative authorship value; and

facilitating a payment of the first disbursement amount to the firstuser.

7. The method of aspect 6, wherein the payment of the first disbursementamount to the first user is automated using account information for afirst user account belonging to the first user of the first digitalaudio workstation.

Sixth Aspect

1. A computer-implemented method, comprising:

identifying, from a user device, a first digital audio workstation(DAW), wherein the first DAW comprises at least an identification of auser of the user device and an audio data file;

determining whether the user of the user device is an authorized user;and

generating a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file.

2. The computer-implemented method of aspect 1, further comprising:

upon detecting an update to the first DAW, determining whether theupdate is performed by the authorized user;

providing a second DAW and a second metadata based on the update to thefirst DAW; and

storing the first DAW, the first metadata, the second DAW, and thesecond metadata.

3. The computer-implemented method of aspect 1, wherein the first DAWand the second DAW comprise at least one of: an application running onthe user device, and a web browser running on the user device.

4. The computer-implemented method of aspect 1, wherein the first DAWand the second DAW are obtained online or offline.

Seventh Aspect

5. An apparatus comprising at least one processor and at least onenon-transitory memory comprising program code, wherein the at least onenon-transitory memory and the program code are configured to, with theat least one processor, cause the apparatus to perform operationsconfigured to at least:

obtain, from a user device, a first digital audio workstation (DAW),wherein the first DAW comprises at least an identification of a user ofthe user device and an audio data file;

determine whether the user of the user device is an authorized user; andgenerate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file.

6. The apparatus of aspect 5, wherein the at least one non-transitorymemory and the program code are configured to, with the at least oneprocessor, further cause the apparatus to perform operations configuredto at least:

upon detecting an update to the first DAW, determine whether the updateis performed by an authorized user;

generate a second DAW and a second metadata based on the update to thefirst DAW; and

store the first DAW, the first metadata, the second DAW and the secondmetadata.

7. The apparatus of aspect 5, wherein the first DAW sand the second DAWcomprise at least one of: an application running on the user device, anda web browser running on the user device.

8. The apparatus of aspect 5, wherein the first DAW and the second DAWare obtained online or offline.

Eighth Aspect

9. A non-transitory computer storage medium, the non-transitory computerstorage medium comprising instructions configured to cause one or moreprocessors to at least at least perform operations configured to atleast:

obtain, from a user device, a first digital audio workstation (DAW),wherein the first DAW comprises at least an identification of a user ofthe user device and an audio data file;

determine whether the user of the user device is an authorized user; and

generate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file.

10. The non-transitory computer storage medium of aspect 9, wherein theinstructions further configured to cause the one or more processors toat least at least perform operations configured to at least:

upon detecting an update to the first DAW, determine whether the updateis performed by an authorized user;

generate a second DAW and a second metadata based on the update to thefirst DAW; and

store the first DAW, the first metadata, the second DAW and the secondmetadata.

11. The non-transitory medium of aspect 9, wherein the first DAW and thesecond DAW comprise at least one of: an application running on the userdevice, and a web browser running on the user device.

12. The non-transitory medium of aspect 9, wherein the first DAW and thesecond DAW are obtained online or offline.

Ninth Aspect

13. A computer-implemented method, comprising:

obtaining, from a user device, a first digital audio workstation (DAW),wherein the first DAW comprises at least an identification of a user ofthe user device and an audio data file;

generating a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file; and

generating a first document based on the first DAW and the firstmetadata, wherein the first document comprises information aboutcopyrights of the audio data file.

14. The computer-implemented method of aspect 13, further comprising:

upon detecting an update to the first DAW, determining whether theupdate is performed by an authorized user;

generating a second DAW and a second metadata based on the update to thefirst DAW;

generating a second document based on the second DAW and secondmetadata, wherein the second document comprises information aboutcopyrights of the second DAW; and

storing the first DAW, the first metadata, the second DAW, the secondmetadata, the first document and the second document.

15. The computer-implemented method of aspect 13, wherein the first DAWand the second DAW comprise at least one of: an application running onthe user device, and a web browser running on the user device.

16. The computer-implemented method of aspect 13, wherein the first DAWand the second DAW are obtained online or offline.

Tenth Aspect

17. An apparatus comprising at least one processor and at least onenon-transitory memory comprising program code, wherein the at least onenon-transitory memory and the program code are configured to, with theat least one processor, cause the apparatus to perform operationsconfigured to at least:

obtain, from a user device, a first digital audio workstation (DAW),wherein the first DAW comprises at least an identification of a user ofthe user device and an audio data file;

generate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file; and

generate a first document based on the first DAW and first metadata,wherein the first document comprises information about copyrights of theaudio data file.

18. The apparatus of aspect 17, further comprising:

upon detecting an update to the first DAW, determine whether the updateis performed by an authorized user;

generate a second DAW and a second metadata based on the update to thefirst DAW;

generate a second document based on the second DAW and second metadata,wherein the second document comprises information about copyrights ofthe second DAW; and

store the first DAW, the first metadata, the second DAW, the secondmetadata, the first document, and the second document.

19. The apparatus of aspect 13, wherein the first DAW and the second DAWcomprise at least one of: an application running on the user device, anda web browser running on the user device.

20. The apparatus of aspect 13, wherein the first DAW and the second DAWare obtained online or offline.

Eleventh Aspect

21. A non-transitory computer storage medium, the non-transitorycomputer storage medium comprising instructions configured to cause oneor more processors to at least at least perform operations configured toat least:

obtain, from a user device, a first digital audio workstation (DAW),wherein the first DAW comprises at least an identification of a user ofthe user device and an audio data file;

generate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file; and

generate a first document based on the first DAW and first metadata,wherein the first document comprises information about copyrights of theaudio data file.

22. The non-transitory medium of aspect 21, further comprising:

upon detecting an update to the first DAW, determine whether the updateis performed by an authorized user;

generate a second DAW and a second metadata based on the update to thefirst DAW;

generate a second document based on the second DAW and second metadata,wherein the second document comprises information about copyrights ofthe second DAW; and

store the first DAW, the first metadata, the second DAW, the secondmetadata, the first document and the second document.

23. The non-transitory medium of aspect 21, wherein the first DAW andthe second DAW comprise at least one of: an application running on theuser device, and a web browser running on the user device.

24. The non-transitory medium of aspect 21, wherein the first DAW andthe second DAW are obtained online or offline.

Twelfth Aspect

25. A computer-implemented method, comprising:

obtaining, from a user device, a first digital audio workstation (DAW),wherein the first DAW is shared by two or more user devices, and whereinthe first DAW comprises at least an identification of a user of eachuser device and an audio data file;

generating a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by eachuser to the audio data file;

calculating a share for each user based on a number of times the audiodata file is streamed or played and the first contribution value by theuser to the audio data file; and

generating a first ledger for the first DAW based at least in part onthe calculated share and the first DAW.

26. The computer-implemented method of aspect 25, further comprising:

upon detecting an update to the number of times the audio data file isstreamed or played, generating a second ledger based on the update tothe number of times the audio data file is streamed or played; and

storing the second ledger.

27. The computer-implemented method of aspect 25, further comprising:

upon a determination that the user of the user device is an authorizeduser, enabling the user to update the first DAW;

generating a second metadata based at least in part on the updated DAW,wherein the second metadata comprises a second contribution value by theuser to the audio data file;

generating a second ledger based at least in part on the updated DAW andthe second metadata; and

storing the first DAW, the first metadata, the updated DAW, the secondmetadata, the first ledger and the second ledger.

28. The computer-implemented method of aspect 27, wherein at least oneof: the first DAW, the updated DAW, the first metadata, and the secondmetadata is retrieved from at least one of: the first ledger, and thesecond ledger.

Thirteenth Aspect

29. An apparatus comprising at least one processor and at least onenon-transitory memory comprising program code, wherein the at least onenon-transitory memory and the program code are configured to, with theat least one processor, cause the apparatus to perform operationsconfigured to at least:

obtain, from a user device, a first digital audio workstation (DAW),wherein the first DAW is shared by two or more user devices, and whereinthe first DAW comprises at least an identification of a user of eachuser device and an audio data file;

generate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file;

calculate a user's share based on a number of times the audio data fileis streamed or played; and

generate a first ledger for the first DAW based at least in part on thecalculated user's share, the first DAW, and the first metadata.

30. The apparatus of aspect 29, wherein the at least one non-transitorymemory and the program code are configured to, with the at least oneprocessor, further cause the apparatus to perform operations configuredto at least:

upon detecting an update to the number of times the audio data file isstreamed or played, generate a second ledger based on the update to thenumber of times the audio data file is streamed or played; and

store the second ledger.

31. The apparatus of aspect 29, wherein the at least one non-transitorymemory and the program code are configured to, with the at least oneprocessor, further cause the apparatus to perform operations configuredto at least:

upon a determination that the user of the user device is an authorizeduser, enable the user to update the first DAW;

generate a second metadata based at least in part on the updated firstDAW, wherein the second metadata comprises a second contribution valueby the user to the audio data file;

generate a second ledger based at least in part on the updated DAW andthe second metadata; and

store the first DAW, the first metadata, the updated DAW, the secondmetadata, the first ledger, and the second ledger.

32. The apparatus of aspect 29, wherein at least one of: the first DAW,the updated DAW, the first metadata, and the second metadata isretrieved from the first the second ledger.

Fourteenth Aspect

33. A non-transitory computer storage medium, the non-transitorycomputer storage medium comprising instructions configured to cause oneor more processors to at least at least perform operations configured toat least:

obtain, from a user device, a first digital audio workstation (DAW),wherein the first DAW is shared by two or more user devices, and whereinthe first DAW comprises at least an identification of a user of eachuser device and an audio data file;

generate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value by theuser to the audio data file;

calculate a user's share based on a number of times the audio data fileis streamed or played; and

generate a first ledger for the first DAW based at least in part on thecalculated user's share, the first DAW, and the first metadata.

34. The non-transitory medium of aspect 33, wherein the instructionsfurther configured to cause the one or more processors to at least atleast perform operations configured to at least:

upon detecting an update to the number of times the audio data file isstreamed or played, generate a second ledger based on the update to thenumber of times the audio data file is streamed or played; and store thesecond ledger.

35. The non-transitory medium of aspect 33, wherein the instructionsfurther configured to cause the one or more processors to at least atleast perform operations configured to at least:

upon a determination that the user of the user device is an authorizeduser, enable the user to update the first DAW;

generate a second metadata based at least in part on the updated firstDAW, wherein the second metadata comprises a second contribution valueby the user to the audio data file;

generate a second ledger based at least in part on the updated DAW andthe second metadata; and

store the first DAW, the first metadata, the updated DAW, the secondmetadata, the first ledger and the second ledger.

36. The non-transitory medium of aspect 33, wherein at least one of: thefirst DAW, the updated DAW, the first metadata, and the second metadatais retrieved from the first the second ledger.

Fifteenth Aspect

37. A computer-implemented method, comprising:

generating a first digital audio workstation (DAW) associated with afirst user device, wherein the first DAW comprises at least one of afirst identification of a user of the first user device, and an audiodata file;

receiving a request from a second user device to access the first DAW;

upon determining that the second user device is an authorized userdevice, granting, to second user device, access to the first DAW;

updating the first DAW by adding a second identification of a user ofthe second user device; and

generating a first metadata based at least in part in the first DAW,wherein the first metadata comprises a first contribution value by thefirst user to the audio data file and a second contribution by thesecond user to the audio data file.

38. The computer-implemented method of aspect 37, further comprising:

upon detecting an update to the first DAW by the first user or thesecond user, generating a second metadata and a second DAW based atleast in part on the update to the first DAW, wherein the secondmetadata comprises a third contribution value by the first user to theaudio data file and a fourth contribution by the second user to theaudio data file; and

storing the first DAW, the second DAW, the first metadata, and thesecond metadata.

39. The computer-implemented method of aspect 37, wherein the first DAWis stored locally on the first user device.

40. The computer-implemented method of aspect 37, wherein the second DAWis stored remotely on a cloud server and shared with the first userdevice and the second user device.

41. The computer-implemented method of aspect 37, wherein generating thesecond metadata and the second DAW is performed in real-time.

42. The computer-implemented method of aspect 37, wherein the first DAWand the second DAW are in communication in real-time or atpre-determined time intervals.

Sixteenth Aspect

43. An apparatus comprising at least one processor and at least onenon-transitory memory comprising program code, wherein the at least onenon-transitory memory and the program code are configured to, with theat least one processor, cause the apparatus to perform operationsconfigured to at least:

generate a first DAW associated with a first user device, wherein thefirst DAW comprises at least one of a first identification of a user ofthe first user device, and an audio data file;

receive a request from a second user device to access the first DAW;

upon determining that the second user device is an authorized userdevice, grant, to second user device, access to the first DAW;

update the first DAW by adding a second identification of a user of thesecond user device; and

generate a first metadata based at least in part in the first DAW,wherein the first metadata comprises a first contribution value by thefirst user to the audio data file and a second contribution by thesecond user to the audio data file.

44. The apparatus of aspect 43, wherein the at least one non-transitorymemory and the program code are configured to, with the at least oneprocessor, further cause the apparatus to perform operations configuredto at least:

upon detecting an update to the first DAW by the first user or thesecond user, generate a second metadata and a second DAW based at leastin part on the update to the first DAW, wherein the second metadatacomprises a third contribution value by the first user to the audio datafile and a fourth contribution by the second user to the audio datafile; and

store the first metadata, the second metadata, the first DAW and thesecond DAW.

45. The apparatus of aspect 43, wherein the first DAW is stored locallyon the first user device.

46. The apparatus of aspect 43, wherein the second DAW is storedremotely on a cloud server and shared with the first user device and thesecond user device.

47. The apparatus of aspect 43, wherein generating the second metadataand the second DAW is performed in real-time.

48. The apparatus of aspect 43, wherein the first DAW and the second DAWare in communication in real-time or at pre-determined time intervals.

Seventeenth Aspect

49. A non-transitory computer storage medium, the non-transitorycomputer storage medium comprising instructions configured to cause oneor more processors to at least at least perform operations configured toat least:

generate a first DAW associated with a first user device, wherein thefirst DAW comprises at least one of a first identification of a user ofthe first user device, and an audio data file;

receive a request from a second user device to access the first DAW;

upon determining that the second user device is an authorized userdevice, grant, to second user device, access to the first DAW;

update the first DAW by adding a second identification of a user of thesecond user device; and

generate a first metadata based at least in part in the first DAW,wherein the first metadata comprises a first contribution value by thefirst user to the audio data file and a second contribution by thesecond user to the audio data file.

50. The non-transitory computer storage medium of aspect 49, wherein theinstructions further configured to cause the one or more processors toat least at least perform operations configured to at least:

upon detecting an update to the first DAW by the first user or thesecond user, generate a second metadata and a second DAW based at leastin part on the update to the first DAW, wherein the second metadatacomprises a third contribution value by the first user to the audio datafile and a fourth contribution by the second user to the audio datafile; and

store the first metadata, the second metadata, the first DAW and thesecond DAW.

51. The non-transitory medium of aspect 49, wherein the first DAW isstored locally on the first user device.

52. The non-transitory medium of aspect 49, wherein the second DAW isstored remotely on a cloud server and shared with the first user deviceand the second user device.

53. The non-transitory medium of aspect 49, wherein generating thesecond metadata and the second DAW is performed in real-time.

54. The non-transitory medium of aspect 49, wherein the first DAW andthe second DAW are in communication in real-time or at pre-determinedtime intervals.

Eighteenth Aspect

55. A computer-implemented method, comprising:

obtaining a first digital audio workstation (DAW), wherein the first DAWcomprises at least an identification of a user of each user deviceassociated with the first DAW and an audio data file;

generating a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value to theaudio data file for the user of each user device; and

calculating, for the user of each user device, a share based on a numberof times the audio data file is streamed or played and the firstcontribution value associated with the user.

56. The computer-implemented method of aspect 55, further comprising:

upon detecting an update to the number of times the audio data file isstreamed or played, recalculating, for the user of each user device, theshare based on the update to the number of times the audio data file isstreamed or played and the first contribution value associated with theuser; and

storing the first DAW, the first metadata, the calculated share for eachuser, and the recalculated share for each user.

Nineteenth Aspect

57. An apparatus comprising at least one processor and at least onenon-transitory memory comprising program code, wherein the at least onenon-transitory memory and the program code are configured to, with theat least one processor, cause the apparatus to perform operationsconfigured to at least:

obtain a first digital audio workstation (DAW), wherein the first DAWcomprises at least an identification of a user of each user deviceassociated with the first DAW and an audio data file;

generate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value to theaudio data file for the user of each user device; and

calculate, for the user of each user device, a share based on a numberof times the audio data file is streamed or played and the firstcontribution value associated with the user.

58. The apparatus of aspect 57, wherein the at least one non-transitorymemory and the program code are configured to, with the at least oneprocessor, further cause the apparatus to perform operations configuredto at least:

upon detecting an update to the number of times the audio data file isstreamed or played, recalculate, for each user of the user device, theshare based on the update to the number of times the audio data file isstreamed or played and the first contribution value associated with theuser; and

store the first DAW, the first metadata, the calculated share for eachuser, and the recalculated share for each user.

Twentieth Aspect

59. A non-transitory computer storage medium, the non-transitorycomputer storage medium comprising instructions configured to cause oneor more processors to at least at least perform operations configured toat least:

obtain a first digital audio workstation (DAW), wherein the first DAWcomprises at least an identification of a user of each user deviceassociated with the first DAW and an audio data file;

generate a first metadata based at least in part on the first DAW,wherein the first metadata comprises a first contribution value to theaudio data file for the user of each user device; and

calculate, for the user of each user device, a share based on a numberof times the audio data file is streamed or played and the firstcontribution value associated with the user.

60. The non-transitory medium of aspect 59, wherein the instructionsfurther configured to cause the one or more processors to at least atleast perform operations configured to at least:

upon detecting an update to the number of times the audio data file isstreamed or played, recalculate, for each user of the user device, theshare based on the update to the number of times the audio data file isstreamed or played and the first contribution value associated with theuser; and

store the first DAW, the first metadata, the calculated share for eachuser, and the recalculated share for each user.

V. Claims

While the specification includes examples, the disclosure's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as examples for embodiments of the disclosure.

Insofar as the description above and the accompanying drawing discloseany additional subject matter that is not within the scope of the claimsbelow, the disclosures are not dedicated to the public and the right tofile one or more applications to claims such additional disclosures isreserved.

What is claimed is:
 1. A method comprising: generating authorshipmetadata in a digital audio workstation for a data file, the digitalaudio workstation associated with at least one smart contract;receiving, from a first user, a first contribution to the data file, thefirst contribution comprising a change in one or more data valuesassociated with the data file; retrieving, from the digital audioworkstation, a first account information related to the first user, thefirst account information comprising authentication information andpersonal information of the first user related to the provisioning ofthe at least one smart contract; evaluating the first contribution toproduce first contribution data; updating, from the first contributiondata a state of a first smart contract; attributing the firstcontribution data with the first account information; recording thefirst contribution data and the first account information in theauthorship metadata of the data file; generating, from the authorshipmetadata a second smart contract comprising information relating to anauthorship of the first user; parsing the authorship metadata of thedata file; deriving, from the authorship metadata, terms comprisingcopyright ownership information relating to the first user; verifying,from the first smart contract and the second smart contract, the termscomprising the copyright ownership information relating to the firstuser; and generating a third smart contract facilitating royaltydisbursement from data verified by the first smart contract and thesecond smart contract.
 2. The method of claim 1, further comprising:receiving from a second user, a second contribution to the data filewithin the digital audio workstation, the second contribution comprisinganother change in the one or more data values associated with the datafile; retrieving, from the digital audio workstation, a second accountinformation related to the second user, the second account informationcomprising authentication information and personal information of thesecond user related to the provisioning of the at least one smartcontract; evaluating the second contribution to produce secondcontribution data; attributing the second contribution data with thesecond account information; modifying the authorship metadata of thedata file based on the second contribution data and the second accountinformation; parsing the authorship metadata of the data file; deriving,from the authorship metadata, the terms comprising the copyrightownership information for the first user and the second user; verifying,from the state of the at least one smart contract, an accuracy of theterms comprising the copyright ownership information relating to thesecond user; and updating the third smart contract facilitating royaltydisbursement from the data verified by the first smart contract and thesecond smart contract.
 3. The method of claim 1, wherein the authorshipmetadata is written onto a media file in the digital audio workstation.4. The method of claim 3, wherein the digital audio workstation hasinformation about the first user and is licensed to the first user. 5.The method of claim 3, wherein the media file is a raw media file. 6.The method of claim 1, further comprising: receiving from a second user,a second contribution to the data file; evaluating the firstcontribution and the second contribution to produce contribution data;and recording the contribution data in the authorship metadata.
 7. Themethod of claim 1, further comprising: receiving, from the plurality ofusers, a plurality of contributions to the data file, the plurality ofcontributions each comprising yet another change in the one or more datavalues associated with the data file; retrieving, from the digital audioworkstation, account information related to a plurality of users, theaccounts information comprising authentication information and personalinformation for each user of the plurality of users related to theprovisioning of the at least one smart contract; evaluating theplurality of contributions to produce contribution data for eachcontribution; updating, from the plurality of contribution data for eachcontribution, the state of the first smart contract; attributing thecontribution data for each contribution to the account information ofeach contributing user of the plurality of users; recording thecontribution data and the account information for each contribution inthe authorship metadata; generating, from the authorship metadata thesecond smart contract comprising information relating to the authorshipof each contributing user of the plurality of users; parsing theauthorship metadata of the data file; deriving, from the authorshipmetadata, the terms comprising the copyright ownership informationrelating to each contributing user of the plurality of users; verifying,from the state of the at least one smart contract, an accuracy of theterms comprising the copyright ownership information relating to eachcontributing user of the plurality of users; and updating the thirdsmart contract facilitating royalty disbursement from the data verifiedby the first smart contract and the second smart contract.
 8. The methodof claim 1, wherein the authorship metadata is recorded on a ledger. 9.The method of claim 1, wherein the authorship metadata is recorded on ablockchain.
 10. The method of claim 1, wherein the authorship metadatais generated within the digital audio workstation.
 11. The method ofclaim 2, wherein the authorship metadata is generated within the digitalaudio workstation and the authorship metadata is modified within adifferent digital audio workstation.
 12. The method of claim 6, whereina plurality of contributions to the data file are made on a plurality oflocal digital audio workstations.
 13. The method of claim 6, wherein aplurality of contributions to the data file are made on a plurality ofremote digital audio workstations.
 14. The method of claim 6, wherein aplurality of contributions to the data file are made using a pluralityof different digital audio workstations the plurality of differentdigital audio workstations networked to a centralized digital audioworkstation, and the method further comprises a selection from thefollowing: reading the authorship metadata using the plurality ofdifferent digital audio workstations from the centralized digital audioworkstation, editing the authorship metadata on the centralized digitalaudio workstation using the plurality of different digital audioworkstations, and changing the authorship metadata on the centralizeddigital audio workstation using the plurality of different digital audioworkstations.
 15. The method of claim 1, wherein the first contributionis evaluated in real time as the first contribution is being made toproduce the first contribution data.
 16. The method of claim 6, whereina plurality of contributions is evaluated using machine learning.